[cod] server log (has to be a bug)

[Henri Mecklin // Coixi]

After you start your server, check the value of g_log. If (when) it's 
000000<x>.log change it to your_desired_logfile.log and make sure that 
it changes (check value of g_log again). Now change map and check value 
of g_log again. For me it stays in the value i set after server start.

What's g_log value in this point for you?

 - Coixi

John Kennington wrote:
> Thanks Henri,
>
> This does not work for me for some reason.  maybe I am doing it 
> wrong.  But this needs to be fixed very soon.
>
> John
>
>
> Henri Mecklin // Coixi wrote:
>> I reported about this yesterday, this is how the bug works and how 
>> you can tempfix it:
>>
>> I start my server using these in cmdline:
>>
>> g_log "games_mp.log"
>> g_logSync "1"
>> logfile "1"
>>
>> When the server starts, it writes first lines to games_mp.log and 
>> console_mp_server.log. Immediately after start, server changes g_log 
>> to "000000<x>.log" where 'x' is random number i've yet not discovered 
>> how it's decided. Anyway, when you first start the server, 'logs' 
>> folder will NOT be created. Server creates the 'logs/000000<x>.log' 
>> after a mapchange (timelimit hit, map_rotate, map mp_*)
>>
>> So here is how you can tempfix it:
>>
>> After you start your server, write to console or via rcon 'g_log 
>> <desired_logname.log>' and the server will keep logging to your own 
>> logfile after mapchange, not to '000000<x>.log'. You only have to do 
>> this once after server start. g_log value will not change 
>> automatically anymore until you restart your server.
>>
>> - Coixi
>>
>> Cpt. Kirk wrote:
>>> John Kennington schrieb:
>>>> Who came up with the idea of saving the game log in /main/logs and 
>>>> automatically incrementing the log number?  Who did that?  I want 
>>>> to meet them so I can beat them with a stick.  This is not workable 
>>>> at all.  This needs fixing post haste.
>>>>
>>>>
>>> :-D
>>> Visit IW.
>>>
>>>
>>
>
>