NetNews Usenet Archive 1993 #1/NN_1993_1.iso/spool/comp/os/vms/20510

Internet Message Format | 1993-01-07 | 1.7 KB

Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!mccall!mccall!tp
Newsgroups: comp.os.vms
Subject: Re: Date incorrect after reboot
Message-ID: <[e-mail]>
From: [e-mail] (Terry Poot)
Date: Thu,  7 Jan 1993 09:02:47 CST
Reply-To: [e-mail] (Terry Poot)
References: <[e-mail]> <[e-mail]> <[e-mail]> <[e-mail]>
Organization: The McCall Pattern Co., Manhattan, KS, USA
Nntp-Posting-Host: mis1
Nntp-Posting-User: tp
Lines: 22


In article <[e-mail]>, [e-mail] (Rob Hooft)
writes:
>Just make sure you have a cluster: good LAVC practice is to
>synchronize the clocks every once in a while: I think SET TIME/CLUSTER
>will also take care of the problem?

I don't think so. SET TIME with no arguments copies the system time into the TOY
clock. SET TIME/CLUSTER synchronizes the cluster, but does NOT copy it into the
TOY clock on any system.

Once, one node of a remote cluster I look after was off by an hour, because I
didn't realize it was down when I adjusted the time after a DST change. I fixed
it by doing SET TIME/CLUSTER from a node that was right. A few days later we
lost power, and when the cluster came back up, that same node was again off by
an hour. I always try to remember now to use sysman to do a SET TIME on each
system after synchonizing the cluster time. One of these days, I'll even look up
the SYSMAN command to do that so I can do all from within SYSMAN. :-)
--
Terry Poot <[e-mail]>                   The McCall Pattern Company
(uucp: ...!rutgers!depot!mccall!tp)          615 McCall Road
[phone], in KS [phone]           Manhattan, KS 66502, USA