Re: insserv: /home on NFS and local bind (DNS lookups fail on boot)
On 2010-08-06 10:01 +0200, Timo Juhani Lindfors wrote:
> nfs:/home /home nfs defaults 0 0
> in /etc/fstab I get
> mount.nfs: Failed to resolve server nfs: Temporary failure in name resolution
> on boot. This is because I use local bind9 and /etc/resolv.conf has
> nameserver 127.0.0.1
And bind9 is started after mountnfs, that's for sure.
> I tried adding " bind9" to the $remote_fs line of /etc/insserv.conf but got
> $ sudo insserv --dryrun
> insserv: There is a loop between service bind9 and rsyslog if started
> insserv: loop involving service rsyslog at depth 8
> insserv: loop involving service bind9 at depth 7
> insserv: loop involving service mountnfs at depth 5
> insserv: loop involving service atd at depth 11
> insserv: exiting now without changing boot order!
Yes, bind9 depends itself on $remote_fs so there is a loop.
> Any idea on how to proceed? I'd hate to use numeric IP addresses.
Changing both bind9's and rsyslog's dependency to $local_fs (either in
the init scripts themselves or in override scripts in
/etc/insserv/overrides) and starting rsyslog and bind9 in runlevel S
This sucks, but it is mainly because Debian's boot system starts the
network in runlevel S already which is IMO wrong but hard to correct.