Managers et al,
I have searched the archives and found a similar problem, but alas no
summary!
Since changeing our zoneinfo for AESOST (Australian Eastern Standard Olympic
Summer Time- or whatever it is now called), 5 of my 21 Tru64 systems are
showing an anomaly in the date. The sytems are all 4.0D-4.0F are all running
xntp3-5.93-xntp 3-5.93e and are all different models.
The problem: Crontab is set to run a number of tasks that are all running 1
hour behind the time they are set to run.
The date command shows the right time and when I implemented the time change
I ran the zic command and confirmed the changes with zdump -v localtime.
Although this is not producing any major hassles, some of the side effects
are annoying e.g. the syslog.dated log files show up as:
drwxr-xr-x 2 root adm 8192 Oct 19 09:00 19-Oct-08:00
drwxr-xr-x 2 root adm 8192 Oct 20 09:00 20-Oct-08:00
drwxr-xr-x 2 root adm 8192 Oct 21 09:00 21-Oct-08:00
drwxr-xr-x 2 root adm 8192 Oct 22 09:00 22-Oct-08:00
drwxr-xr-x 2 root adm 8192 Oct 23 09:00 23-Oct-08:00
drwxr-xr-x 2 root adm 8192 Oct 24 09:00 24-Oct-08:00
drwxr-xr-x 2 root adm 8192 Oct 25 09:00 25-Oct-08:00
Note the hour difference between file datestamp and the file name.
Any suggestions on what is controlling this time or how to fix this problem
would be appreciated and will be summarised.
Regards, John
John Gormley
Senior Unix Systems Administrator
Southern Cross University
Lismore NSW
AUSTRALIA.
jgormley_at_scu.edu.au
Received on Tue Oct 24 2000 - 23:16:32 NZDT