Re^2: TIME::LOCAL from within KSH

What version of "date(1)" are you talking about? My version (MacOSX/darwin, based on bsd) doesn't have a "-d" option at all, and on a freebsd machine, "-d" means "set the kernel's value for daylight savings time". (Looks like the Solaris 5.8's "date" didn't have "-d" either, and on a linux box, "-d STRING" doesn't seem to report seconds since epoch, but date +%s does.)

Just curious...

Comment on Re^2: TIME::LOCAL from within KSH Download Code

Replies are listed 'Best First'.
Re^3: TIME::LOCAL from within KSH by AltBlue (Chaplain) on May 19, 2007 at 11:52 UTC
What version of "date(1)" are you talking about? Sorry, OP didn't mention anything about his/her env. "-d STRING" doesn't seem to report seconds since epoch, but date +%s does "`-d STRING`" will be used for passing custom time, otherwise you'll be formatting the current time ;-) e.g.: `$ date -d '1987-12-18 12:13:14' -u '+%s' 566827994 $ date -d '1987-12-18' -u '+%s' 566784000` [download] -- altblue.	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: TIME::LOCAL from within KSH
by AltBlue (Chaplain) on May 19, 2007 at 11:52 UTC

What version of "date(1)" are you talking about?

Sorry, OP didn't mention anything about his/her env.

"-d STRING" doesn't seem to report seconds since epoch, but date +%s does

"-d STRING" will be used for passing custom time, otherwise you'll be formatting the current time ;-)

e.g.:

$ date -d '1987-12-18 12:13:14' -u '+%s'
566827994
$ date -d '1987-12-18' -u '+%s'
566784000
[download]

--
altblue.

[reply]
[d/l]