It's always nice when somebody provides **JUST EXACTLY** enough information
to allow diagnosing their problem. :-)
You would find it enlightening to look at the invocation of ntpdate in
/etc/rc.d/init.d/xntpd. They do:
/usr/sbin/ntpdate -s -b -p 8 -u `cat /etc/ntp/step-tickers`
The critical option here seems to be the "-u" option:
-----
-u
Direct ntpdate to use an unprivileged port or outgoing packets.
This is most useful when behind a firewall that blocks incoming
traffic to privileged ports, and you want to synchronise with
hosts beyond the firewall. Note that the -d option always uses
unprivileged ports.
-----
Which would explain why it worked in debug mode, but not in normal mode.
pete
> Date: Tue, 23 May 2000 20:39:34 -0700
> From: Barnett Hsu <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: xntpd/ntpdate problem
>
> Hi.
>
> Prior to upgrading from RHL 5.2 to RHL 6.1/6.2, I've
> been using ntpdate from xntpd3 to keep my computer's
> clock accurate. ntpdate runs in my /etc/ppp/ip-up
> script. It was working fine, however, after upgrading
> to 6.1 (and the situation continues in 6.2), neither
> ntpdate nor the xntpd daemon works.
>
> For example, if I do "/usr/sbin/ntpdate -sv tick.cs.unlv.edu"
> (or any other server), the message "no server suitable
> for synchronization found" appears in /var/log/messages.
>
> BUT if I run ntpdate in debug mode on the same servers,
> then it appears to work (but that doesn't set the clock).
> For example, "/usr/sbin/ntpdate -svd clepsydra.dec.com"
> resulted in "step time server 204.123.2.5 offset 158.910853 sec"
> appearing in /var/log/messages.
>
> I'm using the xntp3 RPM from Red Hat 6.2.
>
> What is going on?
pete peterson
GenRad, Inc.
7 Technology Park Drive
Westford, MA 01886-0033
[EMAIL PROTECTED] or [EMAIL PROTECTED]
+1-978-589-7478 (GenRad); +1-978-256-5829 (Home: Chelmsford, MA)
+1-978-589-2088 (Closest FAX); +1-978-589-7007 (Main GenRad FAX)
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
