Bug#769528: systemd: ifup@ services failing if no /run/network directory

[Martin Pitt]

Michael Biebl [2014-11-14 22:57 +0100]:
> Hm, I wonder if we (or better ifupdown) should rather ship a tmpfiles
> snippet for it, or, as I did in the past, ship create the runtime
> directory manually.

I don't think that this would be right. If someone disables
/etc/init.d/networking, then I think we should respect that, i. e. not
run ifupdown, instead of re-enabling it through the backdoor?

> I also found the commit message a bit odd, what did you mean with
> "autogenerated networking.service" ?

Indeed, that's a bit confusing. I suppose he meant "networking.service
that represents /etc/init.d/networking". I adjusted the changelog in
git now:

  * debian/ifup at .service: add a ConditionPath on /run/network, to avoid
    failing the unit if /etc/init.d/networking is disabled. (Closes: #769528)

I hope that's clearer now?

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141115/119cf90d/attachment-0002.sig>