Comment 4 for bug 933566

> 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.

I added touch commands to the scripts which show this.

--------------------------------------------------
pre-start script
 touch /run/resolvconf-started
 mkdir -p /run/resolvconf/interface
 # Request a postponed update (needed in case the base file has content).
 touch /run/resolvconf/postponed-update
 # Enable updates and perform the postponed update.
 resolvconf --enable-updates
end script

post-stop script
 touch /run/resolvconf-stopped
 resolvconf --disable-updates
end script
-------------------------------------------------

After boot:

# status resolvconf
resolvconf stop/waiting
# ls -l /run/resolvconf*
-rw-r--r-- 1 root root 0 2012-02-16 22:37 /run/resolvconf-started
-rw-r--r-- 1 root root 0 2012-02-16 22:37 /run/resolvconf-stopped

/run/resolvconf:
total 4
drwxr-xr-x 2 root root 60 2012-02-16 22:38 interface
-rw-r--r-- 1 root root 0 2012-02-16 22:38 postponed-update
-rw-r--r-- 1 root root 151 2012-02-16 22:37 resolv.conf

Interestingly, another job very much like resolvconf doesn't suffer from this problem:

# cat /etc/init/foo.conf
# upstart script for foo

description "Initialize or finalize foo"

start on mounted MOUNTPOINT=/run

stop on runlevel [06]

pre-start script
 mkdir -p /run/foo
 touch /run/foo/foofile
end script

post-stop script
 mv /run/foo/foofile /run/foo/foofile2
end script

# status foo
foo start/running
# ls -l /run/foo
total 0
-rw-r--r-- 1 root root 0 2012-02-16 22:37 foofile