Hey Cameron, Cameron Norman [2014-05-04 8:19 -0700]: > 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.
I don't think it does. For that the job had to add a condition to start before mounting something else (and I don't think that even exists in upstart). This is mostly there to ensure that it can actually write anything into /run. It's not necessary to translate this to the systemd unit as /run is mounted before systemd runs any unit. > 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 issues. I'm not aware of any issues with this, what do you mean? The crucial thing here is that network-manager starts *after* resolvconf, which is done by n-m's "Before=network.target". Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
