On Wed, 2010-02-03 at 00:05 +0200, Alan McKinnon wrote:
> On Tuesday 02 February 2010 04:06:14 Iain Buchanan wrote:
> > The 50k of messages all look like this:
> That's definitely not right. Even with full debugging enabled no app should
> emit that amount of logs.
and yet with debugging disabled, there's no cpu usage, so perhaps
there's just a problem with my syslog-ng rules?
> Seeing as we are dealing with networkmanager with it's long history of being
> hard to deal with, I recommend you
>
> a. recognize the truth - that it is a piece of shit
I appreciate the humour, but so far for me, it's Just Worked(TM). Even
with this log file annoyance, it's still "working".
> b. use wicd instead, which is decidedly not a piece of shit
I had a look at that, but it doesn't do 2 things that I use
NetworkManager for:
1. mobile broadband (essential for on the road)
2. NetworkManager sends dbus messages that evolution uses to toggle
its online / offline state. I was sick of forever waiting for
evolution to time out because I'd gone offline. (Granted, you
may think evolution is another POS, but it does certain things
that no other mail client can do, but that's another story)
I found a post that suggested in fact iwlagn wasn't reloading properly
after a suspend, so I've added "UnloadModules iwlagn"
to /etc/hibernate/common.conf and so far I haven't seen the spurious log
messages (cross my fingers).
> :-)
thanks,
--
Iain Buchanan <iain at pcorp dot com dot au>
This is the tomorrow you worried about yesterday. And now you know why.
