Am Dienstag, 10. April 2007 22:27 schrieben Sie:
> Erik Thiele wrote:
> > the problem now is that the dhclient sets networking parameters after
> > ntpd has already started. dhclient won't restart ntpd because
> > configuration hasn't changed.
>
> So what is the actual problem? ntp.conf.dhcp is not created, or it
> doesn't contain the right information, or ntpd is not restarted?
ntpd is not restarted is the problem.
>
> > this way ntpd will fail on the ip
> > adress because the ethernet is down.
>
> Why would the ethernet be down after calling dhclient? An why is that
> ntpd's fault?
the ethernet was down before dhclient. ntpd decided that the ntp host is down,
and will not rethink this decission just because the ethernet gets up at some
point in time.
1) from a former run i have correct data in ntpd.conf.dhcp
2) ntpd is running, but networking is not yet brought up, dhcp requests are
not yet replied by the server.
3) ntpd thus tries to contact my old ntp.my.lan server, and finds out that
this does not work. it now decides that the server is broken.
4) dhclient activates networking and finds out that ntpd.conf.dhcp is not
changed, so he does not restart ntpd
5) but ntpd has already decided that the ethernet does not work and will never
rethink it's decission and stay in this mode forever:
ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
wo.x.lan .INIT. 16 - - 64 0 0.000 0.000 0.000
6) i manually restart ntpd and it instantly works.
----> if the configuration file ntpd.conf.dhcp has not changed on dhcp
startup, then anyway ntpd has to be restarted because the actual difference
between before and after dhclient run is that before the ethernet is down and
the host unreachable, and afterwards the ethernet is up and the host is
reachable.
cya
erik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
