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#32753 - [dhcpcd] -b option causes network dependent services to fail
Attached to Project:
Arch Linux
Opened by Dave Reisner (falconindy) - Sunday, 18 November 2012, 16:27 GMT
Last edited by Ronald van Haren (pressh) - Sunday, 18 November 2012, 18:57 GMT
Opened by Dave Reisner (falconindy) - Sunday, 18 November 2012, 16:27 GMT
Last edited by Ronald van Haren (pressh) - Sunday, 18 November 2012, 18:57 GMT
|
DetailsThe -w flag should not have been exchanged for -b in dhcpcd@.service, as it causes systemd to think that the network is available when it really isn't yet. This leads to network dependent services failing on boot. Easily reproducible with an NFS mount in /etc/fstab -- boot will hang until the NFS mount timeout.
It's fine to keep the -b flag in dhcpcd.service, because you can't possibly rely on that service to properly activate network.target, regardless of the flags. |
This task depends upon
Closed by Ronald van Haren (pressh)
Sunday, 18 November 2012, 18:57 GMT
Reason for closing: Fixed
Additional comments about closing: dhdcpd 5.6.3-2
Sunday, 18 November 2012, 18:57 GMT
Reason for closing: Fixed
Additional comments about closing: dhdcpd 5.6.3-2