src-test/etc/rc.d/dhclient, branch main

Move rc startup scripts from etc/ to sbin/init/

2018-07-28T20:36:23Z

This keeps most startup scripts as CONFS per discussion on src-committers from back during BSDCan. Approved by: will (mentor) Differential Revision: https://reviews.freebsd.org/D16466

Allow more services to run in vnet jails

2017-07-08T09:28:31Z

After some tests, here are the services that run into a vnet jail: - defaultroute - dhclient - ip6addrctl - natd - pf - pfsync - pflog (deamon runs, pflog0 interface usable, but /var/log/pflog not filled) - rarpd - route6d (do nothing anyway because obsolete) - routed (do nothing anyway because obsolete) - rtsold - static_arp - static_ndp PR: 220530 Submitted by: olivier@freebsd.org

Fix indentation in dhclient rc.d script

2016-05-31T18:40:47Z

- Add descriptions to most of the rc scripts. Those are mostly taken from their

2016-04-23T16:10:54Z

daemon's manpage and probably improved. - Consistently use "filesystem" not "file system". Approved by: bapt, brueffer Differential Revision: D452

dhclient: don't use syslog for logging non-DHCP interface errors

2012-01-20T17:19:50Z

We should show the error to user, but it doesn't deserve syslog. Approved by: jhb

rc.d: document 'quiet' prefix and fix dhclient/devd interaction

2012-01-12T06:48:11Z

Document the current semantics of the 'quiet' command prefix in the rc.subr(8). Fix dhclient rc.d script: it should not call err() for non-DHCP-enabled interface when it is called from devd, because the latter just blindly calls 'service dhclient quietstart' on each "link up" event. Since the 'quietstart' will silence the message "Cannot 'start' . Set _enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'." and running dhclient on the non-DHCP-enabled interface is the same thing as running the service without _enable set, such modification is in sync with the current semantics of the 'quiet' prefix. Approved by: glebius Reviewed by: freebsd-rc list MFC after: 2 weeks

Fix handling of rc_force in /etc/rc.d/dhclient

2011-10-28T06:03:38Z

Variable 'rc_force' is accessible only at the time of rc_run_command, so it can't be examined from the script's main code. Spotted by: hrs Reviewed by: hrs, des Approved by: des MFC after: 2 weeks

The rc_force test was inverted in the previous commit, so that dhclient ran

2011-10-17T13:05:57Z

for interfaces which were not configured for DHCP *unless* rc_force was set; the correct logic is to run dhclient for those interfaces *only if* rc_force is set. Broken by: des@ Noticed by: everybody and his dog Submitted by: rea@ PR: bin/161733

Make dhclient use a pid file. Modify the rc script accordingly; while

2011-10-13T17:20:45Z

there, clean it up and add some error checks. Glanced at by: brooks@ MFC after: 3 weeks

Add very limited support for the isc-dhclient. It will almostly certaintly

2008-04-15T23:03:35Z

only work if there's just one interface doing dhcp. This version implements the same logic as the version in the PR, but uses pgrep to be less verbose. PR: conf/95905 MFC after: 1 week