named and ntpd start order in rc.d
yuripv at yuripv.net
Sun Aug 26 23:09:57 UTC 2018
Andrea Venturoli wrote:
> I'm in the same situation described in this bug:
> ntpd starts when named is not yet running, fails to resolve its peers
> and never works again until I restart it manually.
This seems to be a real bug here. Sometimes I'm seeing the ntpd whining
about resolve failures on start when I'm doing network maintenance, but
I have never checked if it operates correctly once the nameservers are back.
Did you look into *why* it never works again, and how exactly it doesn't
work -- it still seems to be running and spamming console while it's
unable to resolve?
> That bug (of the 7.0 era) was closed as fixed, since /etc/rc.d/ntpd
> requires ntpdate, which in turn required named.
> However, the latest statement is not true anymore, today (probably due
> to the fact that named is no longer in base).
> I guess I'm not the only one who has this problem and I wonder how
> others are solving this issue.
> Also, should I add a comment to that bug or open a new one?
More information about the freebsd-questions