[Resolvconf-devel] Bug#700846: Service file

Cameron Norman camerontnorman at gmail.com
Sun May 4 15:19:57 UTC 2014

On Sun, May 4, 2014 at 7:24 AM, Martin Pitt <mpitt at debian.org> wrote:
> Hey Thomas,
> Thomas Hood [2014-05-04  8:16 +0200]:
>> Is resolvconf.service releasable? Should I now copy the file
>> /lib/systemd/system/resolvconf.service from Martin Pitt's package to the
>> Debian resolvconf package?
> Not from my side. I uploaded it to Ubuntu a while ago[1] with the
> patch from this bug [2], and have heard no complaints about it being
> broken. It has also worked quite fine here for two weeks, so it
> shouldn't be too bad to start with.

What were the specific complaints? I noticed the Upstart job for
resolvconf has quite a strange start on event, "mounted
MOUNTPOINT=/run". Correct me if I am wrong, but I believe this blocks
mountall from mounting anything else until resolvconf has started,
since mounted is a hook event. The systemd translation of this would
be Before=local-fs.target ; remote-fs.target. This means that
resolvconf in Ubuntu has been starting at very early boot and blocking
many other services from starting, which may tell why the systemd
service, which does not perform that unintentional blocking, is having


More information about the Resolvconf-devel mailing list