Bug#754218: boot hangs forever on LSB job "raise network interfaces"

Michael Biebl biebl at debian.org
Wed Jul 9 00:28:56 BST 2014


Am 09.07.2014 01:14, schrieb Michael Biebl:
> Am 08.07.2014 22:50, schrieb Stefano Zacchiroli:
>> Now the questions/comments:
>>
>> - I've had that script since ever, basically, and it used to work fine
>>   in the past, both before and after switching to systemd as init. I'm
>>   not sure why/when it stopped working.
>>
>> - As a mere user, the above script is perfectly reasonable, I *do* want
>>   to restart my firewall every time my network interface is brought up,
>>   and AFAICT I'm using the right "API" to do so.

Running within the context of an if-up.d hook you make an explicit
assumption that $network is already provided, which is probably reasonable.

Strictly speaking though, the LSB $network facility is defined in
/etc/insserv.conf when the networking (or the old ifupdown) SysV init
script has been fully started, which is not the case during the inital
start of that script.

I'm not sure how to address this. Either the hooks are fixed to not make
this assumption, or the "bring network up" phase proving $network and
"run if-up.d hooks" are split into two different SysV init scripts.

The latter is probably not feasable.






-- 
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: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140709/b1b9c073/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list