Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: noisy dhcpcd messages



On Sat, Nov 05, 2022 at 13:38:34 +0100, Thomas Klausner wrote:
> Date: Sat, 5 Nov 2022 13:38:34 +0100
> From: Thomas Klausner <wiz%NetBSD.org@localhost>
> Subject: Re: noisy dhcpcd messages
> To: current-users%NetBSD.org@localhost
> 
> On Tue, Nov 01, 2022 at 01:29:19PM +0300, Valeriy E. Ushakov wrote:
> > On Tue, Nov 01, 2022 at 10:05:19 +0100, Thomas Klausner wrote:
> > 
> > > What's up with these log lines?
> > > 
> > > Oct 31 07:52:59 yt dhcpcd[3496]: wm0: requesting DHCPv6 information
> > > Oct 31 07:53:52 yt syslogd[4885]: last message repeated 5 times
> > [...]
> > > This is not a new issue, I can find these log lines in my messages
> > > files going back to at least August 31. Does this message have a point
> > > or should we remove it from the default log level?
> > 
> > It is, but in -current,
> 
> Do you mean "it is removed, but in -current"?  That confuses me,
> because these messages I see are on 9.99.104.

Then it's trying to tell you something, I guess :)

The logic in dhcpcd that is in current is to log that message at info
the first time and then to use debug for it unless $reasons.  But my
knowedge of dhcpcd internals is not enough to tell interpret those
reasons in a human readable way...

See dhcp6_startinform external/bsd/dhcpcd/dist/src/dhcp6.c:1651

    if (state->new_start || (state->new == NULL && !state->failed))
       llevel = LOG_INFO;
    else
	llevel = LOG_DEBUG;
    logmessage(llevel, "%s: requesting DHCPv6 information", ifp->name);


> Or syslog has a different bug, because more details from the same log
> file:

You can probably run syslog with debugging enabled, but it looks like
it needs a small fix to be able to specify debug level without
recompilation (the relevant dprintf is for D_DATA, which is not in
D_DEFAULT) - see usr.sbin/syslogd/syslogd.c:331

-uwe


Home | Main Index | Thread Index | Old Index