Re: Restarting ntpd on address change

From: Brooks Davis (brooks_at_one-eyed-alien.net)
Date: 11/30/05

  • Next message: Forrest Aldrich: "Re: device em0 not showing up at boot"
    Date: Tue, 29 Nov 2005 18:19:30 -0800
    To: "Ian D. Leroux" <ian_leroux@fastmail.fm>
    
    
    

    On Tue, Nov 29, 2005 at 09:01:16PM -0500, Ian D. Leroux wrote:
    > Greetings,
    >
    > My machine's ip address is assigned by DHCP, and whenever it changes
    > ntpd stops functioning and must be restarted. I gather this behavior
    > will be changed in some future ntpd version, but in the meantime I had
    > added a line to my /etc/dhclient-exit-hooks to restart ntpd every time a
    > new address was obtained:
    >
    > # [...] setup variables for ipcheck
    >
    > if [ -n "$new_ip_address" ]; then
    > # [...] run ipcheck to update my dyndns
    > /etc/rc.d/ntpd restart
    > fi
    >
    > This seemed work fine on 5.4, but on 6.0 it gives problems at boot.
    > Specifically, I get repeated "bad file descriptor" errors after my
    > network address is assigned, and running ps after the boot completes
    > shows that there are two ntpd processes running. Killing one of them
    > stops the file descriptor errors. My interpretation of this (for what
    > it's worth) is that an ntpd process gets started before dhclient gets a
    > chance to configure the address (perhaps when the interface initially
    > comes up) and then when the address is assigned the /etc/rc.d/ntpd
    > restart starts a second process, but somehow fails to stop the first
    > one. For now I've removed that line from dhclient-exit-hooks, which
    > avoids the problems at boot time.
    >
    > I have the feeling that I'm not doing the Right Thing here. So is there
    > an accepted (or at least known-good) way of automatically managing the
    > restart of ntpd on address change? Have I found a bug in rc.d worth
    > investigating? Or should I just stick to manual restarts until ntpd
    > stops needing them?

    Hmm, this should work because the pid file should prevent ntpd from
    getting started twice. That happens on my -CURRENT laptop so I'm
    thinking there's something going on in the startup process that's
    tripping you up. One thought I had was that /var/run might be getting
    cleared, but it doesn't look like that should be the case.

    On a tangential note, the ntpd script won't actually support chroots due
    to it's broken assumption that devices can exist outside devfs file
    systems.

    --- Brooks

    -- 
    Any statement of the form "X is the one, true Y" is FALSE.
    PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
    
    



  • Next message: Forrest Aldrich: "Re: device em0 not showing up at boot"

    Relevant Pages

    • Re: Restarting ntpd on address change
      ... ntpd stops functioning and must be restarted. ... /etc/rc.d/ntpd restart ... Killing one of them stops the file descriptor errors. ... My interpretation of this is that an ntpd process gets started before dhclient gets a chance to configure the address and then when the address is assigned the /etc/rc.d/ntpd restart starts a second process, but somehow fails to stop the first one. ...
      (freebsd-stable)
    • Restarting ntpd on address change
      ... ntpd stops functioning and must be restarted. ... /etc/rc.d/ntpd restart ... shows that there are two ntpd processes running. ...
      (freebsd-stable)
    • Re: ntpd vs selinux
      ... It appears that the last selinux update has killed ntpd, as shown from my messages log: ... So to get a clean restart, I did a restart, and this error was logged. ... If ntpd is still not working, the problem lies elsewhere than SELinux. ...
      (Fedora)
    • Re: ntpd vs selinux
      ... It appears that the last selinux update has killed ntpd, as shown from my messages log: ... So to get a clean restart, I did a restart, and this error was logged. ... If ntpd is still not working, the problem lies elsewhere than SELinux. ...
      (Fedora)
    • Re: ntpd vs selinux
      ... It appears that the last selinux update has killed ntpd, as shown from my messages log: ... So to get a clean restart, I did a restart, and this error was logged. ... If ntpd is still not working, the problem lies elsewhere than SELinux. ...
      (Fedora)