On Sunday 25 January 2004 08:08, bascule wrote: > joe, > ntpd is both the server and the client, > though to check it use ntpq not ntpdate: > [EMAIL PROTECTED] downloads-linux]$ ntpq > ntpq> peer > remote refid st t when poll reach delay > offset jitter > =================================================================== >=========== LOCAL(0) LOCAL(0) 10 l 55 64 377 > 0.000 0.000 0.015 *sherlock.excess LOCAL(0) 11 u 105 > 512 377 4.873 68.425 33.595 ntpq> quit > [EMAIL PROTECTED] downloads-linux]$ > > in the above output sherlock is my firewall and time server for the > lan, so ntpd is running on that machine and also on my workstation, > mycroft. on mycroft i put the server ip into /etc/ntpd.conf and > into the timeserver /etc/ntpd.conf i put the ip of one of > manchester uni's timeservers , being a firewall of course i also > have to allow traffic on port 123 in both directions! > if i'm right ntpdate is a one off time setter, > it won't keep the time correct and it won't calculate the 'tick' of > the local machine compared to the time server so that if the > timeserver goes down local time is still counted reasonably > accurately > at least i think ntpd does that :) > > bascule
Bascule - so is ntp on the server then running continuously, or is it called by a cron job? Anne -- Registered Linux User No.293302 Have you visited http://twiki.mdklinuxfaq.org yet?
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
