I have one thing to say to myself: patience young grasshopper. I just hadn't let it run long enough before killing it ;-).
I decided to do ntpd -d (debugging mode) and eventually the time was set correctly. Eric. On 5/7/05, Eric Dunbar <[EMAIL PROTECTED]> wrote: > Hello, I've got a server that likes to loose 30 to 60 seconds each > week. I'm trying to get ntpd working but haven't had much success. > > I tried uncommenting the server line in /etc/ntp.conf and changing the > URL to ntp2.cmc.ec.gc.ca before running ntpd from the command line and > it doesn't do much. > > I've now tried a very simple /etc/ntp.conf file: > server ntp2.cmc.ec.gc.ca > > As suggested by the ntp website and that doesn't work. > > (I wait a few mintues, checking system time using 'date' and ntp > activity with ntpstat) > > However, if I run either > ntpdate ntp2.cmc.ec.gc.ca > > or > > ntpd -qd > > The date is updated to the correct time. > > Should ntpd -q be run as a cron job? Seems a little strange for a > daemon to run as a cron job. > > Anyone have experience with ntpd? > > Eric. > _______________________________________________ yellowdog-general mailing list [email protected] http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general HINT: to Google archives, try '<keywords> site:terrasoftsolutions.com'
