DHClient Renewal Logging Change

NOYB

Don't know if it was intentional or not but dhclient logging has recently changed.
No longer logging DHCPREQUEST DHCPACK and bound messages for DHCP renewals.
Now only logging the RENEW and Creating resolve.conf messages for DHCP renewals.

Previously was logging this for DHCP renewals:


Feb 23 20:34:05	dhclient[76347]: DHCPREQUEST on bfe0_vlan98 to d.d.61.1 port 67
Feb 23 20:34:06	dhclient[76347]: DHCPACK from d.d.16.1
Feb 23 20:34:06	dhclient: RENEW
Feb 23 20:34:06	dhclient: Creating resolv.conf
Feb 23 20:34:06	dhclient[76347]: bound to d.d.61.19 -- renewal in 900 seconds.

Now only logging this for DHCP renewals:


Feb 24 14:05:42	dhclient: RENEW
Feb 24 14:05:42	dhclient: Creating resolv.conf

I don't really care one way or the other. Just pointing out the change in case it wasn't intentional or happens to matter to someone.

2.1-BETA1 (i386)
built on Sun Feb 24 04:12:26 EST 2013

The change occurred sometime during the previous week.

stan-qaz

That looks to be a change to the 2.0.3 pre-release too.

2.0.3-PRERELEASE (amd64)
built on Thu Feb 21 18:49:39 EST 2013
FreeBSD 8.1-RELEASE-p13

Feb 24 22:23:39 	dhcpd: DHCPACK on 172.16.2.33 to 00:0e:58:52:79:e2 via em1
Feb 24 22:23:39 	dhcpd: DHCPREQUEST for 172.16.2.33 from 00:0e:58:52:79:e2 via em1

Versus:

2.0.3-PRERELEASE (amd64)
built on Wed Feb 13 12:44:38 EST 2013
FreeBSD 8.1-RELEASE-p13

Feb 23 20:54:15 	dhcpd: DHCPACK on 172.16.2.51 to 00:1d:ba:5a:14:e2 via em1
Feb 23 20:54:15 	dhcpd: DHCPREQUEST for 172.16.2.51 (172.16.0.1) from 00:1d:ba:5a:14:e2 via em1
Feb 23 20:54:15 	dhcpd: DHCPOFFER on 172.16.2.51 to 00:1d:ba:5a:14:e2 via em1
Feb 23 20:54:15 	dhcpd: DHCPDISCOVER from 00:1d:ba:5a:14:e2 via em1
Feb 23 20:54:15 	dhcpd: DHCPOFFER on 172.16.2.51 to 00:1d:ba:5a:14:e2 via em1
Feb 23 20:54:15 	dhcpd: DHCPDISCOVER from 00:1d:ba:5a:14:e2 via em1

wallabybob

@NOYB:

Just pointing out the change in case it wasn't intentional or happens to matter to someone.

The think there is a sufficient number of DHCP related problems reported and a sufficient number of "getting started" problems to warrant restoring the previous behaviour. Alternatively, add a GUI option to REDUCE the verbosity of dhclient logging.