Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Dec 2008 14:42:49 -0800
From:      "Nerius Landys" <nlandys@gmail.com>
To:        RW <fbsd06@mlists.homeunix.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: named and ntpd start order in rc.d
Message-ID:  <560f92640812051442y4263b70and059c0a6e6177cd9@mail.gmail.com>
In-Reply-To: <20081205221113.6084e635@gumby.homeunix.com>
References:  <560f92640811211647q551daccnaec4e8085bb8e042@mail.gmail.com> <20081205190703.0dfb952d@gumby.homeunix.com> <560f92640812051322h520ac67ficebbc3881907fbc2@mail.gmail.com> <20081205221113.6084e635@gumby.homeunix.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> 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 understand why enabling ntpdate in
rc.conf fixed my problem of ntpd's DNS resolver child process not
completing (returning).  My guess was that NETWORK and named were
guaranteed getting run before ntpd if I included ntpdate in rc.conf.
I thought that perhaps NETWORK and named were not getting run before
ntpd in my particular case when I didn't include ntpdate in rc.conf.
But according to your information NETWORK and named scripts would get
run before the ntpd script no matter if ntpdate was enabled in rc.conf
or not (because NETWORK and named are required by ntpdate and ntpdate
is required by ntpd).

So why did enabling ntpdate in rc.conf fix my problem?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?560f92640812051442y4263b70and059c0a6e6177cd9>