[cod] Spamming our logs again

[Silent]

I for now use rsyslog (aptitude install rsyslog). This little entry in 
rsyslog.conf makes the pain an end:

:programname,isequal,"bdLog" ~

This moves all messages from bdLog to /dev/null where it belongs :)

Silent_Water

Marcel wrote:
> Ryan C. Gordon wrote:
>>> It writes to /var/log/messages directly? odd....
>>
>> No, it writes to its own logfile; I don't think we use a syslog 
>> facility at all.
>>
>> It's possible that other programs, like Ubuntu's logger, might be 
>> catching stdout and redirecting to syslog.
>>
>> (I'd have to check, though, maybe I'll be surprised to find some 
>> leftover from quake 3 where it DOES write to syslog...)
>>
>> --ryan.
>
>
> I've also the problem on CentOs 5.
> /var/log/messages is full of bdLog stuff
>
> Mar 15 14:39:41 ms104 bdLog[27432]: 
> ../DemonWare/bdCore/bdContainers/bdBitBuffer.cpp(526): ERROR: 
> Expected: UInt32 , read: NoType
> Mar 15 14:41:13 ms104 bdLog[1438]: 
> ../DemonWare/bdCore/bdContainers/bdBitBuffer.cpp(526): ERROR: 
> Expected: UInt32 , read: NoType
>
>
> etc etc
> _______________________________________________
> cod mailing list
> cod at icculus.org
> http://icculus.org/mailman/listinfo/cod