Date: Thu, 9 Nov 2000 09:13:43 -0800
From: Robert Sweet
On Wed, 8 Nov 2000 22:54:08 -0800, Michael Perry wrote:
| I have a debian box which talks ntpd to a timeserver at clock.via.net. I | then use ntpdate to talk with my box which talks with the timeserver. I | have a cronjob which runs every 2 hours which synchs the time to my box. | Works for me quite well. | | My cron job looks like: | | * */2 /usr/sbin/ntpdate -s 192.168.0.1 |
I am not mistaken, this approach is the wrong way around. ntpdate is used to make an initial sync with a timeserver and xntpd is being run afterwards for the continuous syncing. On other words, one needs to run ntpdate only once (at machine bootime). If you run xntpd hereafter at boottime then xntpd will start itself as a daemon, and will continuously try to sync itself with the timeserver. The ntp protocol will figure out for itself how often it is necessary to sync.
Koos Pol ---------------------------------------------------------------------- S.C. Pol T: +31 20 3116122 Systems Administrator F: +31 20 3116200 Compuware Europe B.V. E: koos_pol@nl.compuware.com Amsterdam PGP public key available
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
My problem is that when I initially sync with a server, which sets the correct time. I get out of sync somehow, yet my hwclock stays correct. For some reason xntpd is not working, yet I see it accessing the servers via ntop. This is what keeps happening: 8 Nov 00:38:21 xntpd[1355]: ntpd exiting on signal 15 8 Nov 11:01:20 xntpd[2543]: signal_no_reset: signal 17 had flags 4000000 8 Nov 14:16:57 xntpd[2542]: time error 7769 over 1000 seconds; set clock manual -- rsweet@socal.rr.com | "I refuse to have a battle of -o) | wits with an unarmed person." Linux, the Choice /\ | of a GNU generation _\_v | |