Mailinglist Archive: opensuse (1599 mails)

< Previous Next >
Re: [opensuse] ntp and wireless
  • From: j debert <jdebert@xxxxxxxxxx>
  • Date: Thu, 29 Oct 2009 07:15:21 -0700
  • Message-id: <4AE9A379.5090400@xxxxxxxxxx>
Why do you need ntp?

Is the system clock severely sloppy about keeping correct time?

Is the CMOS clock a P.O.S.?

Is there something critical that requires zero delta time with some
other system(s)?

Or is it so there is an excuse to neglect the system and CMOS clocks?

If you just want the clock to be adjusted on startup or network
connection, netdate or rdate will do the same thing. Since they're not
daemons, they will not take away any system resources. I seem to
recall ntpd blocking if it tried to reach timeservers when the network
was down or didn't yet exist, among other problems that prompted me to
use rdate and netdate instead.

A script to periodically test the network connection and run netdate
or rdate when the network is up works just fine. The script can also
be run under cron at some suitably long time interval to update system
time. The script can also run hwclock to set the CMOS clock as well. I
used to have it on some boxen with P.O.S. CMOS clocks but the newer
ones have very accurate clocks (approx +/-0.2sec/month) so it's only
necessary to adjust clocks every couple months or so. So all ntp would
do is tie up resources that could better be used for other things.

ntp was created because of the need to keep system clocks accurately
synchronised on a network for some time-critical applications. Most
people do not need it. Even the author discouraged it's use.

There was once an easy to follow adjtime tutorial that made it easy
even for n00bs to adjust the system clock accurately. Anyone know
where it went to? (It's not in the HOW-TO.)

Celebrate Hannibal Day this year. Take an elephant to lunch.

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups