Re: Clock in error in NTP client env.

1996-11-07 Thread Guy Maor
[EMAIL PROTECTED] ( WILLIAM M BURNS) writes: > How does the CMOS clock affect the running system? There must be > some program that reads to CMOS clock and then sets the UNIX clock to > the same value. That program is clock(8). > Is there a way to set the CMOS clock to the UNIX clock without

Re: Clock in error in NTP client env.

1996-11-07 Thread Larry 'Daffy' Daffner
WILLIAM M BURNS writes: -> How does the CMOS clock affect the running system? There must be -> some program that reads to CMOS clock and then sets the UNIX clock to -> the same value. The kernel clock is set from the CMOS clock at boot time through the clock program. Usually, it is not ref

Re: Clock in error in NTP client env.

1996-11-07 Thread WILLIAM M BURNS
How does the CMOS clock affect the running system? There must be some program that reads to CMOS clock and then sets the UNIX clock to the same value. Is there a way to set the CMOS clock to the UNIX clock without bring down the system? Are there even two clocks(UNIX and CMOS)? I have ha

Re: Clock in error in NTP client env.

1996-11-05 Thread Guy Maor
[EMAIL PROTECTED] ( WILLIAM M BURNS) writes: > Does any know of a reason that the local CPU clock would jump forward > 1 hour? Some CMOS can handle daylight savings for you. You want that to be disabled. Guy -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PR

Clock in error in NTP client env.

1996-11-05 Thread WILLIAM M BURNS
Does any know of a reason that the local CPU clock would jump forward 1 hour? We are running as a NTP client and the clocks are in sync with the NTP server. This has run fine for some time. Now, for some unknown reason, the clock jumps forward 1 hour. The NTP server is ok. All the other NTP