OK, so whilst we're gearing up for hopefully the last baselayout-2 release candidate I thought I would pose to the list a question I've been struggling with for some time.
Should hotplugged services affect dependencies by default? (Note, this is not about enabling hotplugged services by default which is another topic for debate. Want to talk about that, start a new thread - but save your breath as I have a laptop and think hotplugging is good :P) By default we've always been YES. But I'm starting now that this should be NO. Rationale for NO Services like openvpn, ssh, dns, etc don't actually care about specific interfaces or addresses as such as they just bind to *. dns may infact be configured to use a resolver that isn't libc so it should be active anway. If say you have nfs mounts, one network cable and then unplug the cable you get this :- netplug calls net.eth0 stop net.eth0 stop calls netmount stop netmount stop tries to unmount the nfs mounts At this point, the process freezes for a LONG time that can't be interupted because as the cable has already been unplugged it can't unmount (if anyone knows how to actually return ASAP I'd like to know that too). With the default to NO the act of pulling the cable simply stops net.eth0 and the services stay up and things continue nicely. For baselayout-1 users, this is the equivalent of having RC_STRICT_NET_CHECKING=lo which a lot of people I've been talking to recently have asked where it is in baselayout-2 Rationale for YES We should only start services like openvpn, ssh, dns, etc when we have a working network devices aside from the loopback. This is the nearest we get to the default baselayout-1 option for RC_STRICT_NET_CHECKING=no Thanks Roy -- [EMAIL PROTECTED] mailing list
