http://qa.mandrakesoft.com/show_bug.cgi?id=4137
------- Additional Comments From [EMAIL PROTECTED] 2003-05-08 14:47 ------- it works again here, it seems that my network card wasn't set up properly, I'm almost sure the problem was that the network script didn't detect MII_NOT_SUPPORTED=yes, and then used ifplugd while it should use ifup. BTW, the manpage of ifplugd isn't accurate anymore with your patch ifplugd-0.14-exit-status.patch ... -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: RESOLVED creation_date: description: There may be a bug in /etc/init.d/network, lines 144-145 : IFPLUGD_ARGS="${IFPLUGD_ARGS=-w -b}" action "Bringing up interface %s: " $i /sbin/ifplugd IFPLUGD_ARGS -i $DEVICE ifplugd is called with -w option, which makes it return 1 on success. >From the man : -w | --wait-on-fork When daemonizing, wait until the background process finished with the initial link beat detection. When this is enabled, the parent process will return the link status on exit. 1 means link beat detected, 2 stands for link beat not detected, everything else is an error. So on success, the result of initlog -c "/sbin/ifplugd IFPLUGD_ARGS -i $DEVICE" is 1, and a failure message is diplsayed. I haven't found any proper way to make initlog return 0 on success of ifplugd with -w option.
