Bug 213018
| Summary: | net/dhcpcd: dhcpcd rc.d script should not provide nostart keyword | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | roy | ||||
| Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Many People | CC: | douglas, milios, seschwar | ||||
| Priority: | --- | Flags: | roy:
maintainer-feedback+
|
||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Committed, thanks! A commit references this bug: Author: swills Date: Thu Nov 9 22:17:49 UTC 2017 New revision: 453875 URL: https://svnweb.freebsd.org/changeset/ports/453875 Log: net/dhcpcd: remove nostart keyword from rc script PR: 213018 Submitted by: roy@marples.name (maintainer) Changes: head/net/dhcpcd/Makefile head/net/dhcpcd/files/dhcpcd.in this breaks things. as of the above commit, dhcpcd, if simply installed and left unconfigured (read: not even enabled in rc.conf[.et al]) it will nonetheless start at boot time, call out to DHCP servers on every hot network port and possibly fall back to choosing an ip in the link local subnet, either way, wiping out any static network configurations on those ports.
to fix, you need to add the following two lines into the rc.d/dhcpcd script [at the appropriate places]
rcvar=dhcpcd_enable
: ${dhcpcd_enable="NO"}
|
Created attachment 175193 [details] Remove nostart keyword from dhcpcd rc script Hi When I originally made the dhcpcd rc.d script, I basically used the dhclient script as a template. Today, dhcpcd is very capable of running from rc itself instead of being triggered from a 3rd party and as such the nostart keyword can e safely removed.