-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Thursday 2007-08-16 at 14:16 -0700, Sloan wrote:
> Carlos E. R. wrote:
> >
> > The Thursday 2007-08-16 at 11:48 -0700, Sloan wrote:
> >
> > >>> rcntpd restart
> > >> Which will not work at all if he is not using ntpd.
> > > IIUC the discussion concerned how to best restart ntpd. The OP was
> > > concerned about the accuracy of time on his linux system, and ntpd (or
> > > periodic ntpdate) is the obvious answer.
> >
> > No, it isn't. Not if he has a missaligned "/etc/adjtime", as he surely
> > has, and that is not solved by restarting ntpd a hundred times. Everytime
> > he boots up the time would be bad again.
> I've not seen that condition in 10 years among the few hundred linux
> boxes here, but should /etc/adjtime actually be defective, one could
> just nuke it and be good to go. I'd be more concerned with the root
> cause, i.e. how did /etc/adjtime get corrupted in the first place.
Then you haven't been reading the list during the past ten years, because
the condition has been reported here several times :-P
Go ahead, search the archive: how /etc/adjtime becomes missaligned or
defective on a SuSE system has been explained here several times. It is
documented, too.
Also, remember that there are many PCs out there without a permanent
network connection, for which running ntpd is not an option. Nevertheless,
keeping the clock reasonable accurate is possible.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFGxez/tTMYHG2NR9URAtKOAJ91cdJJR/2aHY7X1pp8b1oMj+4TsgCgjPmw
6Jr81BB9E74ngvoqAP3pc60=
=0uqb
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
