The issue seems to revolve around the upstart scripts, I attempted to
rewrite sections of the scripts so that the service would start at later
(higher) run level but to no effect. The issue is not with DNS
resolution of the domain though. Something is wrong when network-manager
initializes the
I was able to circumvent this issue by removing the network-manager
package and managing devices manually.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.net/bugs/1007273
Title:
autofs does
I have encountered this too while trying to put together an image for
12.04.1 LTS kernel 3.2.0-31-generic. Same premise, upstart fails to
correctly initialize autofs (5.0.6-0ubuntu5) on boot because of ypbind
wait-for-state issues but it doesn't seem to be related to dnsmasq
(server is NOT managed
