Date: Thu, 06 Feb 2014 17:44:17 -0500 From: "Mike." <the.lists@mgm51.com> To: freebsd-questions@freebsd.org Subject: Re: dhclient and 10.0 Message-ID: <201402061744170611.021C490B@smtp.24cl.home> In-Reply-To: <201402061340490129.013D609C@smtp.24cl.home> References: <201402061340490129.013D609C@smtp.24cl.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/6/2014 at 1:40 PM Mike. wrote: |I wrote a simple dhclient-exit-hooks script consisting only of the |following three lines: | | | logger -t deh entering dhclient-exit-hooks | env | logger -t deh | logger -t deh leaving dhclient-exit-hooks | | |So far I've been using IPv4 DHCP only. | |When the lease on the IP address is renewed or changes, I see entries |in the messages log corresponding to those three lines. | |However, when the computer first boots up, I do not see any entries |in the messages log for the initial run of dhclient during the boot |process. | |I'd like to see those entries, but I cannot find a configuration |parameter that instructs dhclient to call the dhclient-exit-hooks |script during the inital running of dhclient. | |rc.conf contains: | | ifconfig_fxp0="DHCP" | dhclient_program="/sbin/dhclient" | | | |Am I missing something else that needs to be in rc.conf? ============= After taking a different approach, I found the answer ... The dhclient-exit-hooks does indeed run when dhclient is invoked during the boot cycle. The issue is that syslogd does not seem to be logging yet. If I create a file inside of dhclient-exit-hooks, then that file is present as a result of dhclient-exit-hooks running during the boot cycle. Sorry for the noise....
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402061744170611.021C490B>