Re: [SLE] List mail still not working for me!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


The Monday 2006-10-30 at 13:11 -0500, Ed McCanless wrote:

Basil Chupin wrote:

My time (clock) is never more than 0.03 seconds out from the atomic
clock.

How do you do that?

Probably the same way as I do it: by running the NTP daemon.

- --
Cheers,
Carlos E. R.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFFRl7itTMYHG2NR9URAoiwAJ9gADsJuNfEhAwwQi2sh12lsoihWwCfTgv0
OmWCJMNYx6CTBcUWOEGF+hg=
=G7Ow
-----END PGP SIGNATURE-----


--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Relevant Pages

  • Re: [opensuse] ntp can not manage to put the clock in sync.
    ... On Thursday 06 December 2007 17:38, Carlos E. R. wrote: ... remember that the system time does not use the cmos clock ... Then you have the luck of getting a pretty good crystal. ... similarly excessive clock drift problem. ...
    (SuSE)
  • Re: [opensuse] ntp can not manage to put the clock in sync.
    ... Carlos E. R. wrote: ... Have you considered that the backup battery ... remember that the system time does not use the cmos clock and ... That's a different clock altogether. ...
    (SuSE)
  • Re: [opensuse] 10.2 system clock too fast and NTP
    ... always running and always correcting ntpd. ... /etc/ntp.conf but once you do that if your clock is close at boot time it will keep it in sync forever. ... I have the ntp daemon configured with a working server, and it produces no error logs. ...
    (SuSE)
  • Re: [opensuse] 10.2 system clock too fast and NTP
    ... always running and always correcting ntpd. ... /etc/ntp.conf but once you do that if your clock is close at boot time it will keep it in sync forever. ... I have the ntp daemon configured with a working server, and it produces no error logs. ...
    (SuSE)
  • Re: "runtime went backwards" message in logs
    ... Not sure if this have anything to do with it (the message mentions CPU ... > time, not the clock), but I'm running a ntp daemon, to synchronize time... ... on net after an outage, & the systems noticed drifted time & corrected etc. ...
    (freebsd-stable)