[ntp:questions] Re: Queries on master time server using local clock

Richard B. Gilbert rgilbert88 at comcast.net
Wed Jun 1 11:25:45 UTC 2005

NewBie wrote:

>The ntp.conf of the master time server using local clock contains the 
>fudge stratum 13
>As a master time server using system time on the current machine, the syntax 
>is (reference 
>http://www.ntp.org/ntpfaq/NTP-s-refclk.htm#Q-LOCAL-CLOCK) but in my master 
>time server, it is set to127.127.1.0. Is there any difference?
>If the master time server booted up after 2 hours of shutdown (switch off) 
>and it's time is 2 hours earlier, what could be wrong?
>Server: SUN
>OS: Solaris 8
>ntpq> version
>ntpq 3-5.93e
>Thanks in advance for any pointer. 
The obvious conclusion is that your hardware clock stopped when you 
powered the machine down!   The clock, and the battery that powers it 
when AC power is off, are encapsulated in the NVRAM chip on most Sun 
hardware.   If the hardware is old enough and has been powered off for 
extended periods, the battery could be failing.

Try shutting down and entering "watch clock" at the OBP prompt.   That 
should show if the clock is still ticking and at what rate.  If it's not 
running or not ticking at approximately one second per second, have Sun 
fix it!

The other possibility is that it was two hours off when you shut it 
down!  There is nothing at all to act as a check on the local clock!!!!!

More information about the questions mailing list