[cod] Spamming our logs

[|T-OC|Morpheus|:.]

The "+set dedicated 1" never worked on cod4, even with last patch (I've 
had no success at this time). As it seems cod5 is based on 1.0 cod4, 
don't expect it to work...

Quint Smit a écrit :
> This Demonware spam? Did ruined our private lan a bit :|
>
> Without a internet connection the codwaw wouldn't run :(  (showing errors
> about demonware url etc. not resolving etc.)
> Lucky enough we managed to run a windows server console (we noticed same
> problem on a windows pc, but not this one)
>
> I think you are suppose to be able to run a private codwaw lan server with
> the linux without a internet connection.
>
> Grtz,
>
> aMaze
>
> -----Oorspronkelijk bericht-----
> Van: INFO [mailto:info at gamestats.info] 
> Verzonden: zondag 1 maart 2009 13:01
> Aan: cod at icculus.org
> Onderwerp: Re: [cod] Spamming our logs
>
> The DemonWare spam? It was added in the 1.2 codedrop (I don't know if
> that's disabled on the Windows console, though).
>
> --ryan.
>
> --------------------------------------------------
> From: "Silent" <silent at ccmail.cc>
> Sent: Saturday, February 28, 2009 9:46 PM
> To: <cod at icculus.org>
> Subject: Re: [cod] Spamming our logs
>
>   
>> Thanks for the hint and your help. Yes I can do this, another ducktape and
>>     
>
>   
>> baling wire fix.
>>
>> I run a script that parses the log every five minutes to count the error 
>> messages of punkbuster and restart it when there are too much 
>> malfunctioning clients (about every hour).
>>
>> Another script pings the server and restarts it if it is not pingable 
>> withing 1 minute (about every 2-3 hours).
>>
>> The yesterdays log was about 36MB. What else should I fix to keep this 
>> bullshit running?
>>
>> I rather would shut down this crap but it seems to be a lot of people 
>> liking this game. Our server is on rank 14 at gametracker and always full.
>>
>> Pretty please with sugar on top:
>> Treyarch fix this issues! I even can keep my fingers on all the holes of 
>> the sieve.
>>
>> Silent_Water
>>
>>
>> Marco Pannekens wrote:
>>     
>>> Really, not funny, but how about some filter entries in your syslog
>>> configuration files to ignore this logging? If you are using syslog-ng 
>>> something
>>> like:
>>>
>>> # new filter definition
>>> filter f_bdlog      { program(bdLog); };
>>>
>>> # filter /var/log/localmessages with the new filter
>>> filter f_local      { facility(local0, local1, local2, local3,
>>>                                local4, local5, local6, local7) and not 
>>> filter
>>> (f_bdlog); };
>>>
>>> # filter /var/log/messages with the new filter
>>> filter f_messages   { not filter(f_bdlog); };
>>>
>>> # following entries should already exist in a similar manner
>>> destination localmessages { file("/var/log/localmessages"); };
>>> log { source(src); filter(f_local); destination(localmessages); };
>>>
>>> destination messages { file("/var/log/messages"); };
>>> log { source(src); filter (f_messages); destination(messages); };
>>>
>>>
>>> might prevent spamming your logfiles.
>>>
>>> McPan
>>>
>>>
>>> Silent schrieb:
>>>
>>>       
>>>> We are running CoD WaW Linux 1.2.
>>>>
>>>> Tonight it spammed our log with this message EVERY SECOND:
>>>>
>>>> started at:
>>>>
>>>> Feb 28 03:34:12 R14573 bdLog[11815]:
>>>> ../DemonWare/bdLobby/bdLobbyConnection.cpp(648): WARNING: Connection
>>>> timed out
>>>> Feb 28 03:34:12 R14573 bdLog[11815]:
>>>> ../DemonWare/bdLobby/bdLobbyService.cpp(512): Disconnected from
>>>> MatchMaking Service.
>>>> Feb 28 03:41:12 R14573 bdLog[11815]:
>>>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>>>> ...
>>>> Feb 28 06:20:15 R14573 bdLog[11815]:
>>>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>>>> Feb 28 06:20:15 R14573 bdLog[11815]:
>>>> ../DemonWare/bdLobby/bdLobbyService.cpp(293): WARNING: Not connected.
>>>> ...
>>>> an so on...
>>>>
>>>> This is NOT FUNNY, Treyarch!
>>>>
>>>> Please correct this - a hot fix was announced for this week. Today is
>>>> saturday and I see no hotfix.
>>>>
>>>> Well I've read the offical statement about the patch here:
>>>> http://www.fpsadmin.com/forum/showthread.php?p=70908
>>>>
>>>> We are not amused about this.
>>>>
>>>> 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
>>>
>>>
>>>       
>> ---
>> 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
>
>
>
> ---
> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38
>
>
>