On Thu, Feb 16, 2012 at 09:43:44PM -0000, Thomas Hood wrote: > > until we know why resolvconf is failing to start for you on boot
> We know that the resolvconf job starts, otherwise /run/resolvconf > wouldn't exist. The problem is that the job also get stopped. No, the job *tries* to start. It is not "started" unless the pre-start script completes successfully. When the pre-start script instead exits non-zero (because it's run under sh -e and one of the commands has failed - presumably the last), the job is then unwound to a "stopped" state. So since the mkdir/touch commands are obviously succeeding, we need to see the output of the resolvconf command to see what's going on here. Per <https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/929552/comments/18>, current precise upstart + a reboot should give you this in /var/log/upstart/resolvconf.log. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933566 Title: Stopping resolvconf doesn't disable updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/933566/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
