hellow, unix-gurus,
I know that Unix 3.2g is not y2k-compliant, bur we must continue to run it
anyways.
Yesterday (29-FEB) everything still worked perfectly, but today the at command
shows a curious behaviour:
date
Wed Mar 1 11:53:38 MET 2000
at "11:55 Mar02,2000" ./sl.test
job root.951908100.a at Wed Mar 01 11:55:00 2000
We use the at command in several procedures, e.g. in the procedure for our daily
backup.
Has anyone any idea hoe we can convince "at" to use exactly the day we have and
nothing else??
Regards Steffi
Received on Wed Mar 01 2000 - 12:31:21 NZDT