Re: named and ntpd start order in rc.d

2008-12-05 Thread RW
On Sat, 06 Dec 2008 01:11:38 +0100 cpghost <[EMAIL PROTECTED]> wrote: > RW wrote: > > I have a similar issue with PPP not having connected by the time > > ntpdate runs , so I just have a script that runs between named and > > ntpdate, and blocks waiting for access. > > > Those timing / start-o

Re: named and ntpd start order in rc.d

2008-12-05 Thread cpghost
RW wrote: On Fri, 21 Nov 2008 16:47:50 -0800 "Nerius Landys" <[EMAIL PROTECTED]> wrote: I believe that the fix for this is to add a dependency to /etc/rc.d/ntpd script, adding "named" to "REQUIRE" section in comments. In your opinion, is this a robust fix? For example the line in my /etc/r

Re: named and ntpd start order in rc.d

2008-12-05 Thread Nerius Landys
> That's not correct. BEFORE and REQUIRE are used by rcorder to > determine the ordering of the scripts without checking if they are > enabled. Actually all scripts get run - if you don't enable ntpdate then > rc.d/ntpdate still runs, but doesn't do anything. My mistake. But then I don't unders

Re: named and ntpd start order in rc.d

2008-12-05 Thread RW
On Fri, 5 Dec 2008 13:22:29 -0800 "Nerius Landys" <[EMAIL PROTECTED]> wrote: > > This shouldn't be needed as ntpd already requires ntpdate and in > > turn ntpdate requires named. The issue is probably timing - that > > named isn't ready. > > Actually, the REQUIRE thing in the /etc/rc.d scripts

Re: named and ntpd start order in rc.d

2008-12-05 Thread Nerius Landys
> This shouldn't be needed as ntpd already requires ntpdate and in > turn ntpdate requires named. The issue is probably timing - that named > isn't ready. Actually, the REQUIRE thing in the /etc/rc.d scripts means "if the required service is enabled, start it before this one". It does not mean "

Re: named and ntpd start order in rc.d

2008-12-05 Thread RW
On Fri, 21 Nov 2008 16:47:50 -0800 "Nerius Landys" <[EMAIL PROTECTED]> wrote: > > I believe that the fix for this is to add a dependency > to /etc/rc.d/ntpd script, adding "named" to "REQUIRE" section in > comments. In your opinion, is this a robust fix? For example the > line in my /etc/rc.d/nt

Re: named and ntpd start order in rc.d

2008-12-03 Thread Greg Larkin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nerius Landys wrote: >> FreeBSD 7.0. I am having a problem when ntpd starts at bootup. It >> continues to have 2 processes running, the process which does the DNS lookup >> fails to exit, and ntpd fails to adjust the clock even after days of >> runni

Re: named and ntpd start order in rc.d

2008-12-03 Thread Chuck Swiger
On Dec 3, 2008, at 1:01 PM, Nerius Landys wrote: [ ... ] Does anyone know why I'm getting 2 ntpd processes running after bootup (and ntpd fails to adjust the clock as a result)? Any suggested fix would be appreciated. When ntpd first starts up, it forks a child process to perform DNS resolut

Re: named and ntpd start order in rc.d

2008-12-03 Thread Nerius Landys
> When ntpd first starts up, it forks a child process to perform DNS > resolution of the timeservers listed in its config. If that fails, that > generally indicates that DNS was not working at the time, or something else > was going wrong with the network. > > [ See ntpd/ntp_config.c, search for f

Re: named and ntpd start order in rc.d

2008-12-03 Thread Nerius Landys
> I don't know why those processes are hung after boot, but in order to > troubleshoot the problem, I suggest that you modify the /etc/rc.d/ntpd > script to invoke ntpd from truss and log the output to a file, e.g. > /tmp/truss.log.$$. Once you've rebooted, kill the processes and post > the the lo

Re: named and ntpd start order in rc.d

2008-12-03 Thread Nerius Landys
>> FreeBSD 7.0. I am having a problem when ntpd starts at bootup. It >> continues to have 2 processes running, the process which does the DNS lookup >> fails to exit, and ntpd fails to adjust the clock even after days of >> running. Immediately after bootup and several hours or days later this i

Re: named and ntpd start order in rc.d

2008-12-03 Thread Nerius Landys
> FreeBSD 7.0. I am having a problem when ntpd starts at bootup. It > continues to have 2 processes running, the process which does the DNS lookup > fails to exit, and ntpd fails to adjust the clock even after days of > running. Immediately after bootup and several hours or days later this is >

Re: named and ntpd start order in rc.d

2008-11-22 Thread Mel
On Saturday 22 November 2008 01:47:50 Nerius Landys wrote: > Trying to reproduce problem. On a running system. I shut down named. Then > I restart ntpd, then I start named. I can reproduce the problem that > happens on bootup - ntpd has 2 processes and does not adjust the clock. > Restarting nt

named and ntpd start order in rc.d

2008-11-21 Thread Nerius Landys
FreeBSD 7.0. I am having a problem when ntpd starts at bootup. It continues to have 2 processes running, the process which does the DNS lookup fails to exit, and ntpd fails to adjust the clock even after days of running. Immediately after bootup and several hours or days later this is what I get