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#17634 - [dhclient] does not change cwd to / when daemonizing
Attached to Project:
Arch Linux
Opened by Mathieu Boespflug (mboes) - Tuesday, 29 December 2009, 10:15 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 17 January 2010, 15:09 GMT
Opened by Mathieu Boespflug (mboes) - Tuesday, 29 December 2009, 10:15 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 17 January 2010, 15:09 GMT
|
DetailsDescription:
The latest dhclient in extra does not change current directory to "/" when daemonizing. This is a problem for instance when running netcfg from a directory that is part of a remote filesystem. It then becomes impossible to unmount the filesystem without first killing dhclient. Looking in the changelog of the dhclient releases, I notice that from dhclient-4.0.0a2 all binaries change the current working directory to "/" when daemonizing, so upgrading the dhclient in extra is one solution to this bug. Additional info: * package version(s) : dhclient-3.1.2p1-3 * config and/or log files etc. Steps to reproduce: # cd /some/random/dir # ifconfig eth0 up # dhclient eth0 # fuser /some/random/dir |
This task depends upon
Closed by Isenmann Daniel (ise)
Sunday, 17 January 2010, 15:09 GMT
Reason for closing: Fixed
Additional comments about closing: dhclient updated to 4.1.0p1
Sunday, 17 January 2010, 15:09 GMT
Reason for closing: Fixed
Additional comments about closing: dhclient updated to 4.1.0p1