Re: ntp: not synchronized?
* Karsten M. Self (kmself@ix.netcom.com) spake thusly:
> on Sun, Aug 05, 2001 at 06:43:07PM -0500, ktb (ktb@nixnotes.org) wrote:
>
> > I guess I was under the impression that ntpdate snagged it's info from
> > ntp servers generally running on port 123. I just assumed it would
> > return on the same port. Guess that is a wrong assumption.
>
> Generally. A listening port is where a process listens for incoming
> traffic. For example, 80 is where your webserver sits. Traffic to 80
> will be intercepted by apache (or alternative). Your outgoing web
> queries sit at some port above 1024, and *send* queries to 80.
> Responses are directed to whatever port the outbound request went to.
> ntpdate is presumably similar.
>
> > There is the "-u" option for ntpdate which might be useful -
>
> Thanks, I'd missed that. Still doesn't work though.
What does 'ntpdate -d ...' say?
Dima
--
E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home)
http://www.bmrb.wisc.edu/descript/gpgkey.dmaziuk.ascii -- GnuPG 1.0.4 public key
One distinguishing characteristic of BOFHen is attention deficit disorder.
Put me in front of something boring and I can find a near-infinite number
of really creative ways to bugger off. -- Antony De Boer in asr
Reply to: