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

[Michael Biebl]

Hi,

Am 14.11.2014 um 12:35 schrieb Martin Pitt:
> Control: tag -1 pending
> 
> Bonjour Didier,
> 
> Didier Roche [2014-11-14 11:51 +0100]:
>> If networking.service wasn't activated (due to, for instance, no symlink in
>> /etc/init.d/networking not having start symlinks in any /etc/rc*.d/), then
>> there is no /run/network directory created.
>>
>> However, systemd still instantiate and starts ifup@*.service units, which
>> are
>> failing due to the lack of /run/network directory. Consequence is that the
>> system is seen as being in degraded mode.
>>
>> We can make ifup@ template have a Conditional Path on /run/network.
> 
> Thanks! Applied with some minor whitespace/changelog adjustments:
> http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=e8bc109667

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 also found the commit message a bit odd, what did you mean with
"autogenerated networking.service" ?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141114/64e05488/attachment-0002.sig>