On 27 Mar 2006 11:54:32 -0800, "Mikhail Zotov" <muxaul@lenta.ru> wrote:

>Grant, I don't have an answer to your post but an info.
>
>I am having two Slackware-current machines with almost identical
>configuration. Both have an /etc/localtime file and a symlink
>/etc/localtime-copied-from . The main difference between the machines
>is that one of them is running 24/7 while the other one is up only for
>a few hours a day. The point is that the "24/7" machine updated its
>clock but the other one did not. Perhaps, one should run Slack 24/7
>:-)

Not the issue, we (the land downunder) just hosted Commonwealth Games
and 'they' (the Govt.) decided to delay DST turnoff for a week. But
slackware's 10.2 had the old DST timing, even though the file was dated
Sep'05.

Solution was to copy slack-current's timezone info over. This is
a one-off issue affecting Eastern Australian States for a week...

Firewall is up 24/7 and is ntp synchronised, the problem is the other
boxen have the wrong timezone offset file, that's all. Next week it
doesn't matter. I may leave them turned off for another week

Grant.
--
Memory fault -- brain fried