Eric Blake wrote:
-----BEGIN PGP SIGNED MESSAGE-----
According to Enrique Arizón Benito on 9/9/2008 4:45 AM:
||# ||date -s "1970-01-01 00:00:01"
Thanks for the report. In which way does it not work? What error
message, if any, is printed? What did you expect to happen, when compared
to what actually happened?
Upps, I forgot it.
#date -s "1970-01-01 00:00:01"
date: cannot set date: Invalid argument
Thu Jan 1 00:00:01 CET 1970
Curiosly after the Invalid argument error, date properly prints the new
hour but doesn't change it.
That's what makes me think it's really a bug.
In general any hour value amongst 01-23 works. 00 fails!
||Is that the expected behaviour?
It's hard to say without more details. Perhaps your timezone is a factor,
where all times 01:00:00 and above normalize to a positive number of
seconds since the epoch, but where 00:00:01 normalizes to a time less than
zero given your current timezone, and your system rejects attempt to set
time to a negative value?
Is there any way to known which timezone date uses?
My system environment variables have nothing related to time zone.
/etc/timezone indicates "Europe/Paris". I remove such file and log in
but the same error arises.
Regards and thanks in advance for your help!
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Bug-coreutils mailing list