Date: Sun, 24 Nov 2002 20:31:28 -0600 From: David Kelly <dkelly@HiWAAY.net> To: questions@FreeBSD.ORG Subject: Re: dhclient too verbose in /var/log/messages Message-ID: <200211242031.28111.dkelly@HiWAAY.net> In-Reply-To: <MIEPLLIBMLEEABPDBIEGAECDDAAA.barbish@a1poweruser.com> References: <MIEPLLIBMLEEABPDBIEGAECDDAAA.barbish@a1poweruser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 24 November 2002 09:38 am, JoeB wrote: > You have to change the level keyword in /etc/syslog.conf to select > or not to select what type of messages you want to log. The level > describes the severity of the message, and is a keyword from the > following ordered list (higher to lower): emerg, alert, crit, err, > warning, notice, info and debug. You may want to start with warning > as notice, info, and debug generates the kind of general operational > msgs you are seeing. For more details read the man page on > syslog.conf Thank you but you missed the point. I don't want to change the messages syslogd traps and writes to files. Its just fine the way it is. OTOH something changed in the past year with dhclient and/or both ISP's I have systems connected via. Something changed which causes dhclient to spit out excess messages in such a way as to cause syslogd to write them to /var/log/messages. If I were to muffle the syslog levels logged I would then risk failing to log something I should not miss. In the case of dhclient its verbosity is predictable and redundant. So now that I've seen this message too much its time to put an end to this one source and leave everything else well enough alone. Considering how top-posting ruined this thread for proper continuance I'll repeat the original situation; /var/log/messages is being flooded with this: Nov 24 16:23:44 grumpy dhclient: New Network Number: 24.214.34.0 Nov 24 16:23:44 grumpy dhclient: New Broadcast Address: 24.214.34.255 Nov 24 17:36:47 grumpy dhclient: New Network Number: 24.214.34.0 Nov 24 17:36:47 grumpy dhclient: New Broadcast Address: 24.214.34.255 Nov 24 18:51:32 grumpy dhclient: New Network Number: 24.214.34.0 Nov 24 18:51:32 grumpy dhclient: New Broadcast Address: 24.214.34.255 Nov 24 20:05:52 grumpy dhclient: New Network Number: 24.214.34.0 Nov 24 20:05:52 grumpy dhclient: New Broadcast Address: 24.214.34.255 It is not a fault for syslogd to be recording these messages. It is an error in dhclient for claiming these parameters have changed when they have not changed. "man dhclient" and "man dhclient.conf" make no mention of how to control logging. No metion of what priority, facility, or level is used when writing log entries. Sadly this is a typical Unix documentation shortcoming. Is also a shortcoming in syslogd in that the logs it writes do not include any hint as to what parameter triggered its filter (syslog.conf) and caused the item to be written to a log file. The solution is to insert a specific sed filter in syslog.conf to delete this excessive verbosity. Or to fix dhclient either by patch or dhclient.conf. But once again the dhclient man pages fail to metion logging as a configurable parameter. Am I the only one who gets these messages every time dhclient renews my lease? -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211242031.28111.dkelly>