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.
current precise upstart + a reboot should give you this in
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 address hidden> <email address hidden>