Roy Marples <[EMAIL PROTECTED]> writes: > 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.
To avoid that problem, do not stop net.ethN when the cable is pulled. When the cable is re-inserted then (if it has not been left disconnected for too long) if the services have not stopped, TCP sessions may still be active. If the user manually stops an interface, by all means stop the services depending on it but (a) Do not make the interface stop automatically when the cable is disconnected, (b) It would be nice if there was a single command which could restart all the dependencies which were stopped. -- [EMAIL PROTECTED] mailing list
