On Tuesday 02 February 2010 04:06:14 Iain Buchanan wrote: > On Fri, 2010-01-29 at 17:29 +0200, Alan McKinnon wrote: > > On Friday 29 January 2010 16:26:42 Iain Buchanan wrote: > > > I don't really care about any killswitch operation, but I'm interested > > > in why I'm getting a "." message. NetworkManager bug or > > > misconfiguration error? > > > > > > Run syslog-ng with the -d switch to enable it's debug output (normally > > to messages), or use -dd to get even more debug output. > > > > Beware, this adds up real quick, so don't run it for long like that. The > > output may give you more of a clue as to what syslog-ng thinks the > > incoming messages are. > > Holy Debug Messages, Batman! Sure does add up real quick. > > 56,599 messages all with the same timestamp Feb 2 11:13:00; 100% cpu > usage, and 200+Mb before I killed it. > > Shirley that's not right? > > The 50k of messages all look like this: > > Feb 2 11:12:59 orpheus syslog-ng[3739]: Filter rule evaluation begins; > filter_rule='f_networkmanager' Feb 2 11:12:59 orpheus syslog-ng[3739]: > Filter node evaluation result; filter_result='not-match' Feb 2 11:12:59 > orpheus syslog-ng[3739]: Filter rule evaluation result; > filter_result='not-match', filter_rule='f_networkmanager'
That's definitely not right. Even with full debugging enabled no app should emit that amount of logs. 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 b. use wicd instead, which is decidedly not a piece of shit :-) -- alan dot mckinnon at gmail dot com
