Re: killswitch messages flood syslog fixed

[Dan Williams <dcbw redhat com>]

On Sun, 2007-11-11 at 20:15 -0500, Walter Neumann wrote:
> On Sun, 11 Nov 2007, Aaron Konstam wrote:
> 
> > On Sun, 2007-11-11 at 12:26 -0500, walter neumann wrote:
> >> Sorry if this has already been said -- I couldn't find any search
> >> functionality for this list.  There have been several messages
> >> complaining that killswitch error messages flood the syslog
> >> (especially on Dell machines that have no physical wlan killswitch,
> >> only the keyboard one).
> >>
> >> The following fixes the problem for me: run on startup
> >>
> >> hal-device --r dell_wlan_switch
> >
> > Well I tried this putting the line in rc.local on my Dell laptop. It
> > seemed to reduce the:
> >
> > Nov 11 16:07:48 cyrus last message repeated 11 times
> >
> > messages but I am still not clear about what is going on, and why this
> > formula helps things.
> 
> I'm not an expert, but the reason for the messages seems to be that 
> NetworkManager tries to query the hardware wireless switch and fires off 

Right, because at present the only way you can figure out killswitch
state is to poll them.

> an error message when it fails.  I suspect this is a hal bug -- hal should 
> probably not provide the device if it is physically absent. But 

That would be the best solution.

> NetworkManager could be nicer by querying the device once to see if it 
> exists and then shutting up about it if it doesn't.

Transient errors can cause failures of the killswitch state query
against HAL, so the better solution is one I've done for 0.7 where NM
stores the last error message from HAL and only prints the same error
message once.

Dan

> Anyway, the command in question removes the device from hal, so 
> NetworkManager does not see it and query it.
> 
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list