Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#7204 - ifplugd: ifplugd.action searches for dhcpcd.pid in the wrong directory
Attached to Project:
Arch Linux
Opened by Apollon Oikonomopoulos (apoikos) - Friday, 18 May 2007, 18:31 GMT
Last edited by Kevin Piche (kpiche) - Tuesday, 17 July 2007, 17:54 GMT
Opened by Apollon Oikonomopoulos (apoikos) - Friday, 18 May 2007, 18:31 GMT
Last edited by Kevin Piche (kpiche) - Tuesday, 17 July 2007, 17:54 GMT
|
Details/etc/ifplugd/ifplugd.action is searching for dhcpcd.pid in /etc/dhcpc/. However, it seems that the PID files for dhcpcd have moved to /var/run. When a DHCP-enabled interface loses link beat, ifplugd can't kill dhcpcd, and subsequently, when the interface comes back up, a new instance of dhcpcd refuses to run. As a result, after unplugging and re-plugging the network cable for the first time, the interface doesn't acquire a new IP Address. The attached patch resolves the issue
|
This task depends upon
Closed by Kevin Piche (kpiche)
Tuesday, 17 July 2007, 17:54 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 0.28-4
Tuesday, 17 July 2007, 17:54 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 0.28-4
Comment by Loic Nageleisen (lloeki) -
Tuesday, 03 July 2007, 13:49 GMT
may I suggest this should rather be fixed in task 7555 way, so as to avoid this kind of issue in the future.
Comment by Kevin Piche (kpiche) -
Tuesday, 17 July 2007, 17:54 GMT
Fixed using the method suggested in task 7555.
ifplugd.action.patch