My original question was:
>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??
My thanks go to (in the order I received answers)
Lucio Chiapetti
Jim Belonis
Bryan Lavelle
Dr. Tom Blinn
Alan Davis
Roland Sieger
Cyndi Smith
I got several advices on how to avoid the at command, hints to some URLs on
Y2k-patches
and the opinion that only an upgrade could help.
The answer that did it for me came from Tom Blinn:
It is unlikely that the "at" from V4.0D will work on V3.2G.
Well, I tried it nevertheless - and it works (in 3.2, 3.2d and 3.2g, as far as I
tested)! Great!!!
Thanks to all!
Steffi
Received on Wed Mar 08 2000 - 07:36:21 NZDT