kts@quintro.uucp (Kenneth T. Smelcer) (01/27/91)
I have a problem with the program 'timed' and how it works under
Domain/OS (SR 10.2 and 10.3).
Our network is a mixture of machines running SR 10.1, 10.2, and 10.3, with
the SR10.1 machines being Mentor graphics stations.
We are running 'timed' on the non-Mentor machines with no problems.
The problem arises when the machine is brought down using either the
/etc/shutdown command or from typing SHUT at the DM Command prompt.
The machine will shut down properly, but when we try to re-boot it,
the machine comes back with a message saying the system clock is more
than 5 minutes ahead of the time stored on the hard disk.
Why doesn't the OS write the proper time to the disk? (It works fine when
timed hasn't changed the system clock.) Does the OS use a different clock
from what 'timed' is adjusting? Is there any way to synchronize them?
--
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
Ken Smelcer Glenayre Corp. quintro!kts@lll-winken
Quincy, IL tiamat!quintro!kts@uunet