# Bcc: control tags 400337 + wontfix thanks On 06/11/25 15:53 +0100, Maik Zumstrull said ... > The quick fix is to change the order scripts are run in, i.e. keep the > interfaces up until remote file systems have been unmounted.
This wouldn't help because ifplugd is supposed to work even in scenarios like where the connection between a switch and the laptop interface is a bit flaky. e.g. how can ifplugd start all the network dependant services whenever the interface is up and stop them when the interface is down? > For a more complete solution, ifplugd should also handle remote file systems > during normal operation: If the cable is pulled, it should check if any > file servers with mounted file systems became unreachable due to this and > do a lazy/forced unmount of these systems, so that requests onto these > systems can fail instead of hanging. The best way of doing this is from /etc/network/if-up.d (start service) and /etc/network/if-down.d (stop service). It would be impossible for ifplugd to cater to all network services that have to started/stopped when the network interface goes up/down. Giridhar -- Y Giridhar Appaji Nag | http://www.appaji.net/
signature.asc
Description: Digital signature
