Hello Ben, and LenZ I am using eastern -local time , I'm in Florida (est) . I changed the time server names to ip numbers , as LenZ suggested. Run Top , kill xntpd , and then restart it. then I ran ntpdate and got - [11:05pm][Thu May 3][basslake:/root]# ntpdate 3 May 23:06:00 ntpdate[1303]: no servers can be used, exiting Now I ran , ntpdate 131.216.16.9 and got [11:22pm][Thu May 3][basslake:/etc]# ntpdate 131.216.16.9 3 May 23:23:02 ntpdate[1921]: the NTP socket is in use, exiting Now I ran Top , kill xntpd - to shut it off completly . Now running ntpdate 131.216.16.9 gave a good result [11:23pm][Thu May 3][basslake:/etc]# ntpdate 131.216.16.9 3 May 23:22:07 ntpdate[1923]: step time server 131.216.16.9 offset -90.534378 sec Since I am not connected to the net at boot-up, It Looks like I don't need to call xntpd at boot-up at all . It seems to be having problems resolving the time-server ip probably no connection at boot-up, causes xntpd to set the time servers as unreachable, and never tries again to access them again. I'll try running ntpdate from kppp , when I dial out ,and set xntpd in rc.config to no. As long as ntpdate works to keep the time accurate, then that is what I wanted. I'm still curious about xntpd though, it is probably more useful to perminant connections than to dial-ups. Hey, yes thanks again for the tips & info - I was unaware of that ntpdate command. JohnWM SuSE7.0 - 2.4.2-4GB - >[windomaker]< - <Gnome - <kde - <kde2 - fvwm2< - ALSA-ymfpci - < On Thu, 03 May 2001, Ben Rosenberg wrote:
I had the problem below when Linux was set to GMT..after I set it to local time..this issue went away and it would synch. *shrug*
- LenZ Grimmer (grimmer@suse.de) [010503 14:31]: }=}On Wed, 2 May 2001, basslake wrote: }=} }=}> I use dial-up account, so when I boot up, I am not connected to the net. }=}> xntp exits , and log says that - }=}> }=}> May 2 11:30:30 basslake ntpdate[389]: can't find host sundial.columbia.edu }=}> May 2 11:30:30 basslake ntpdate[389]: can't find host tick.cs.unlv.edu }=}> May 2 11:30:30 basslake ntpdate[389]: no servers can be used, exiting }=} }=}This is no good. Maybe it cannot resolve the host names? Maybe you should }=}try to use IP addresses instead. }=} }=}> May 2 11:30:30 basslake xntpd[392]: ntpd 4.0.99f Mon Apr 9 10:57:57 GMT 2001 ( }=}> May 2 11:30:30 basslake xntpd[392]: signal_no_reset: signal 13 had flags 400000 }=}> May 2 11:30:30 basslake xntpd[392]: precision = 11 usec }=}> May 2 11:30:30 basslake xntpd[392]: kern_enable is 1 }=}> May 2 11:30:30 basslake xntpd[392]: using kernel phase-lock loop 0040 }=}> May 2 11:30:30 basslake xntpd[392]: frequency initialized 0.000 from /etc/ntp.d }=}> May 2 11:30:30 basslake xntpd[392]: using kernel phase-lock loop 0041 }=}> }=}> Question: Do I need to stop, then restart xntpd every time I go on }=}> line ? , or is there a command-line command to tell xntpd to get the }=}> time sync from the net servers ? }=} }=}I would recommend to start and stop it every time you go online/offline. }=}Since it cannot sync the clock while you are offline anyway, there is not }=}much use for keeping it running. Anyway - how exact do you want your }=}system clock to be? I simply run "ntpdate" every time I connect to the }=}net. It's not like the clock is going to drift for hours if you are }=}disconnected for a day :) }=} }=} LenZ }=}-- }=}------------------------------------------------------------------ }=} Lenz Grimmer SuSE GmbH }=} mailto:grimmer@suse.de Schanzaeckerstr. 10 }=} http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany }=} One who is always in a stew generally goes to pot. }=} }=} }=}-- }=}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 and the }=}archives at http://lists.suse.com }=}
-- Ben Rosenberg mailto:ben@whack.org
If two men agree on everything, you can be sure that only one of them is doing the thinking.
-- 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 and the archives at http://lists.suse.com