Starting with sys-apps/baselayout-1.12.0_pre10-r1, the network dependant services which are stopped before bringing down the interface when issuing `/etc/init.d/net.eth0 restart` are not restarted when the network is brought back up in the background.
this has been filed already, just not sure of the bug number
I couldn't find any relevant bug - and Uberlord asked me to open this.
looks like Bug 80785 to me
(In reply to comment #3) > looks like Bug 80785 to me No, that deals with bringing down the interface and then later bringing it back up. I'm talking about restarting the interface using `/etc/init.d/net.eth0 restart`. This works in <1.12.0_pre10-r1, but the immediate backgrounding in _pre10-r1 breaks this behavior.
I'm in two minds about this. If you restart a network service that brings itself up in the background (ie it returns straight away allowing for a faster boot) then should it restart the depending services when it comes up? One solution would be to create a move the snapshot.$$ folder to snapshot.$service if $service is inactive so when $service is "up" then it can restart things ok. On the other hand, there is no guarantee that the service will come up.
Well, this behavior changed in pre10-r1. Why not just restore the behavior of pre10?
Actually we just changed the default timeouts to -1 for ifplugd, netplugd and wpa_supplicant
The issue here is the default timeout. -1 returns instantly, so the interface is "inactive" and not "started". If enough people are unhappy with this behaviour then we will change the default back to 60 seconds.
*** Bug 112762 has been marked as a duplicate of this bug. ***
*** Bug 113312 has been marked as a duplicate of this bug. ***
Fixed in SVN -will be in baselayout-1.12.0_pre14
pre14 is out
Verified with baselayout-1.12.0_pre14. Thanks :)
