[cod] Spamming our logs again

[Geoff Goas]

i wonder which syslog facility its using?

On Tue, Mar 10, 2009 at 1:07 PM, |T-OC|Morpheus|:. <morpheus at clantoc.org>wrote:

> The only messages remaining is the errors, but so much errors give us
> almost the same result : SPAMMING !!
>
> So far, is it possible to redirect all this crap to a dedicated logfile
> (dware.log in example) ? As my public cod2 server is randomly crashing
> following pb updates and map incompatibilities, it becomes quite harder to
> catch up the segfaults...
>
> It has been done once, please can you do this again Ryan ?
>
> PS : I ask this but I'm totally unaware about the architecture of the
> demonware bloat (all I know is that real customers get more trouble than
> pirates, again).
>
> Silent a écrit :
>
>  We are running CoD WaW Linux 1.3 fully patched
>>
>> Last night we got another Logspam:
>> ...
>> Mar 10 06:25:38 ROOT2 bdLog[7429]:
>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>> Mar 10 06:25:38 ROOT2 bdLog[17110]:
>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>> Mar 10 06:25:38 ROOT2 bdLog[7429]:
>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>> Mar 10 06:25:38 ROOT2 bdLog[17110]:
>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>> Mar 10 06:25:38 ROOT2 bdLog[7429]:
>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>> Mar 10 06:25:38 ROOT2 bdLog[17110]:
>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>> Mar 10 06:25:38 ROOT2 bdLog[7429]:
>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>> Mar 10 06:25:38 ROOT2 bdLog[17110]:
>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>> ...
>> Some thousands entries blowed up our logfile to 20MB.
>>
>> I thought this issue has been fixed with patch 1.3???
>>
>> Why don't you write this messages to error output on console like any
>> other message?
>>
>> Thanks in advance for another patch really solving this issue...
>>
>> Silent_Water
>>
>>
>> ---
>> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
>> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38
>>
>>
>>
> ---
> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38
>
>
>


-- 
Geoff Goas
Network Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20090310/6db40840/attachment.htm>