[Resolvconf-devel] Bug#700846: Fixed and tested .service and debdiff
Cameron Norman
camerontnorman at gmail.com
Wed Apr 23 15:26:35 UTC 2014
On Wed, Apr 23, 2014 at 7:06 AM, Martin Pitt <martin.pitt at ubuntu.com> wrote:
> Hey Cameron, Thomas,
>
> I ran into resolvconf being broken with systemd as when NetworkManager
> starts it sees the dangling /etc/resolv.conf symlink and replaces it
> with a file. So I looked into this and uploaded a fixed version of
> this into my PPA (https://launchpad.net/~pitti/+archive/systemd)
Do you know of any other services which behave in that way? We would
need to make sure they have an After=network.target as well, then.
>> RemainAfterExit=yes
>> ExecPreStart=/bin/mkdir -p /run/resolvconf/interface; /bin/touch /run/resolvconf/postponed-update
>
> ExecStart* are not shell commands, so this causes some havoc: it
> creates a dir "interface;", another dir /bin/touch (which fails), and
> the third dir. It's better to write that as two commands.
Strange, I thought you could do that. I saw it in one of the plymouth
services, I think. I hope that is not broken.
> Thanks,
>
> Martin
>
> --
> Martin Pitt | http://www.piware.de
> Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Thank you,
--
Cameron Norman
More information about the Resolvconf-devel
mailing list