10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
i have a folder, with tons of files containing as following,
on /my/folder/jobs/
some_name_2016-01-17-22-38-58_some name_0_0.zip.done
some_name_2016-01-17-22-40-30_some name_0_0.zip.done
some_name_2016-01-17-22-48-50_some name_0_0.zip.done
and these can be lots of similar files,... (6 Replies)
Discussion started by: charli1
6 Replies
2. Shell Programming and Scripting
awk -v now="$(date +%s)" -v tDiff="${USERMINUTES}" '
BEGIN {
FS="="
if (!now) now=systime()
if (!tDiff) tDiff=60*60
p=1
}
/{/ {rec=$0;p=1;next}
/}/ && rec && p {print rec ORS $0;next}
$1=="entry_time" { if (now-$2>tDiff)p=0 }
{rec=rec ORS $0}'... (6 Replies)
Discussion started by: SkySmart
6 Replies
3. Shell Programming and Scripting
Need a ksh script to get the files that were created or modified in a directory on a particular date entered by the user.
For example if a directory contains files as below :
> ll
total 41
-rw-rw-r-- 1 psn psn 199 Aug 23 07:06 psn_roll.sh
-rw-rw-r-- 1 psn psn ... (10 Replies)
Discussion started by: ramprabhum
10 Replies
4. UNIX for Dummies Questions & Answers
I need my code to compare two different files that are in two completely different directories, How can I do this?
So for example, my code will look at file1 which is in my home directory, and compare the files with those from file2 that is in /abc/adf/adr/afc/adf/file2... does that make sense? (1 Reply)
Discussion started by: castrojc
1 Replies
5. Shell Programming and Scripting
Hi all,
Have to generate an xml having information related to files in the directory
Suppose i have file
file1.xml (datafile)
file2.xml (datafile)
file3.xml (metafile)
Now i need to generate an xml in the format >>
<?xml version="1.0" encoding="UTF-8"?>
<AuditFile Version="2.0">... (8 Replies)
Discussion started by: abhinav192
8 Replies
6. UNIX for Dummies Questions & Answers
Hello All,
Got a question to make a script what reads a directory and put the file names from that directory in a file with some extra text.
ls /tempdir
output is:
file1.gfh
file2.txt
file4.zzz
these file names (always with an extention) must be placed in a line and written to... (2 Replies)
Discussion started by: ToXiQ
2 Replies
7. Shell Programming and Scripting
I have list of files named file_username_051208_025233.log. Here 051208 is the date and 025233 is the time.I have to run thousands of files daily.I want to put all the files depending on the date of running into a date directory.Suppose if we run files today they should put into 05:Dec:08... (3 Replies)
Discussion started by: ravi030
3 Replies
8. HP-UX
Hi all,
I want to know date information on unix about 105th day's date from today's date. (2 Replies)
Discussion started by: megh
2 Replies
9. UNIX for Dummies Questions & Answers
hi,
say I have
dirA/file1
dirB/file2
and I tar them up, and then do
zcat Tar.tar | tar tvf -
Sometimes I will see:
dirA/
dirA/file1
dirB/
dirB/file2
yet other times I will see (4 Replies)
Discussion started by: JamesByars
4 Replies
10. UNIX for Dummies Questions & Answers
Basically i have done created the script below, and it functions ok, it prints the access rights the user has. But i need it to print the group permissions, and other permissions, it would also be helpful if i could print the permissions in numeric form aswell, if it is possible. I have looked in... (50 Replies)
Discussion started by: Makaveli.2003
50 Replies
DNSSEC-SETTIME(8) BIND9 DNSSEC-SETTIME(8)
NAME
dnssec-settime - Set the key timing metadata for a DNSSEC key
SYNOPSIS
dnssec-settime [-f] [-K directory] [-L ttl] [-P date/offset] [-A date/offset] [-R date/offset] [-I date/offset] [-D date/offset] [-h]
[-v level] [-E engine] {keyfile}
DESCRIPTION
dnssec-settime reads a DNSSEC private key file and sets the key timing metadata as specified by the -P, -A, -R, -I, and -D options. The
metadata can then be used by dnssec-signzone or other signing software to determine when a key is to be published, whether it should be
used for signing a zone, etc.
If none of these options is set on the command line, then dnssec-settime simply prints the key timing metadata already stored in the key.
When key metadata fields are changed, both files of a key pair (Knnnn.+aaa+iiiii.key and Knnnn.+aaa+iiiii.private) are regenerated.
Metadata fields are stored in the private file. A human-readable description of the metadata is also placed in comments in the key file.
The private file's permissions are always set to be inaccessible to anyone other than the owner (mode 0600).
OPTIONS
-f
Force an update of an old-format key with no metadata fields. Without this option, dnssec-settime will fail when attempting to update a
legacy key. With this option, the key will be recreated in the new format, but with the original key data retained. The key's creation
date will be set to the present time. If no other values are specified, then the key's publication and activation dates will also be
set to the present time.
-K directory
Sets the directory in which the key files are to reside.
-L ttl
Sets the default TTL to use for this key when it is converted into a DNSKEY RR. If the key is imported into a zone, this is the TTL
that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence.
Setting the default TTL to 0 or none removes it.
-h
Emit usage message and exit.
-v level
Sets the debugging level.
-E engine
Use the given OpenSSL engine. When compiled with PKCS#11 support it defaults to pkcs11; the empty name resets it to no engine.
TIMING OPTIONS
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the argument begins with a '+' or '-', it is interpreted as an offset
from the present time. For convenience, if such an offset is followed by one of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the
offset is computed in years (defined as 365 24-hour days, ignoring leap years), months (defined as 30 24-hour days), weeks, days, hours, or
minutes, respectively. Without a suffix, the offset is computed in seconds. To unset a date, use 'none'.
-P date/offset
Sets the date on which a key is to be published to the zone. After that date, the key will be included in the zone but will not be used
to sign it.
-A date/offset
Sets the date on which the key is to be activated. After that date, the key will be included in the zone and used to sign it.
-R date/offset
Sets the date on which the key is to be revoked. After that date, the key will be flagged as revoked. It will be included in the zone
and will be used to sign it.
-I date/offset
Sets the date on which the key is to be retired. After that date, the key will still be included in the zone, but it will not be used
to sign it.
-D date/offset
Sets the date on which the key is to be deleted. After that date, the key will no longer be included in the zone. (It may remain in the
key repository, however.)
-S predecessor key
Select a key for which the key being modified will be an explicit successor. The name, algorithm, size, and type of the predecessor key
must exactly match those of the key being modified. The activation date of the successor key will be set to the inactivation date of
the predecessor. The publication date will be set to the activation date minus the prepublication interval, which defaults to 30 days.
-i interval
Sets the prepublication interval for a key. If set, then the publication and activation dates must be separated by at least this much
time. If the activation date is specified but the publication date isn't, then the publication date will default to this much time
before the activation date; conversely, if the publication date is specified but activation date isn't, then activation will be set to
this much time after publication.
If the key is being set to be an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it
is zero.
As with date offsets, if the argument is followed by one of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the interval is
measured in years, months, weeks, days, hours, or minutes, respectively. Without a suffix, the interval is measured in seconds.
PRINTING OPTIONS
dnssec-settime can also be used to print the timing metadata associated with a key.
-u
Print times in UNIX epoch format.
-p C/P/A/R/I/D/all
Print a specific metadata value or set of metadata values. The -p option may be followed by one or more of the following letters to
indicate which value or values to print: C for the creation date, P for the publication date, A for the activation date, R for the
revocation date, I for the inactivation date, or D for the deletion date. To print all of the metadata, use -p all.
SEE ALSO
dnssec-keygen(8), dnssec-signzone(8), BIND 9 Administrator Reference Manual, RFC 5011.
AUTHOR
Internet Systems Consortium
COPYRIGHT
Copyright (C) 2009-2011 Internet Systems Consortium, Inc. ("ISC")
BIND9 July 15, 2009 DNSSEC-SETTIME(8)