[Info-vax] Clock running very slow on an Alpha

Peter Weaver info-vax at weaverconsulting.ca
Thu Aug 26 08:42:16 EDT 2010


> Is the clock rate steady ? You could run a recurring bacth job that
> would adjust the clock by a few seconds every 15 minutes, and let NTP do
> the rest.

I am running ntpdate every 5 minutes (based on that Alpha's clock) and the
clock resets about 2.8 to 3.4 seconds each time. 

> Question:
>
> when you do SET TIME, does it update the TOY clock, or does it use the
> TOY clock value to update the internal clock ?

I tried that once, the VMS time was about 10 minutes slow before I issued
the command, the time was about 5 minutes slow after issuing the SET TIME
command.

> If there were a way to read the TOY clock value and use it as the VMS
> time, it may also provide a temporary solution with recurring bacth job
> to reset the system clock. (I realise that TOY is no longer the proper
> terminilogy for Alpha, but you know what I mean).

SET TIME/CLUSTER fixes the time when I issue the command from another node,
so does 
MCR SYSMAN
SET ENV/CLUS
CONFIG SET TIME



Peter Weaver
Certified OpenVMS System Administrator
Certified OpenVMS System Engineer
Winner of the OpenVMS.org Readers' Choice Award for System
Management/Performance
http://www.weaverconsulting.ca
http://www.linkedin.com/in/peterweaver





More information about the Info-vax mailing list