# Bcc: control severity 306797 normal thanks Hi Martin, On 05/04/29 12:02 +0200, Martin Steigerwald said ... > Am Donnerstag 28 April 2005 18:57 schrieb Oliver Kurth: > > Well, this is not a bug. ifplugd's purpose is to run as a daemon, and > > bring up an interface whenever you plug in a cable. This means your > > setup should also work when you boot your laptop without a cable plugged > > hmmm, of course. Now I remember placing some chrony script > in /etc/network/if-up.d in order to switch chrony online when a network is > detected on my private laptop. > > But still I do not understand why usually /etc/init.d/ifplugd waits until ifup > has finished the interface configuration and sometimes it does not. Given > your explaination it shouldn't wait at all or when "-w" is given not longer If there is a script in /etc/network/if-up.d and the cable is present, that would be executed post link detection because ifplugd would do an ifup on the interface. I am guessing there may have been a difference in the packages installed on the two machines, hence the behaviour. The bug is quite old, but I am hoping we would be able to figure this out with more information. I am lowering the priority of this bug to normal. > Well it seems this issue really needs some thought. Probably it would be good > to file bug reports for network service related packages that have > no /etc/init.d/if-up.d and /etc/init.d/if-down.d scripts that operate well > with the usual boot sequence init script calling procedure. Yes, and over time packages seem to supply scripts there. Cheers, Giridhar -- Y Giridhar Appaji Nag | http://www.appaji.net/
Attachment:
signature.asc
Description: Digital signature