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

[Henri Mecklin // Coixi]

So did i.

You're right, it can't change to config_mp_server.cfg but the value of 
that dvar can still change without writing it to a config file.



Quint van Drosthagen wrote:
> I made the config_mp_server.cfg readonly so it can't be changed...;-)
>
> -----Original Message-----
> From: Evans, James C (N-HiTec Associates) [mailto:james.c.evans at lmco.com] 
> Sent: vrijdag 28 april 2006 16:05
> To: cod at icculus.org
> Subject: RE: [cod] server log (has to be a bug)
>
>
> I just use the +set fs_homepath and +set fs_basepath commands in my
> commandline and haven't had any trouble....always writes to the correct
> log file without doing anything.... 
>
>
> ------------------------------------------------------------------------
> ------------
> James Evans
> Lockheed Martin
> Aircraft Sustainment - Donaldson Site
> james.c.evans at lmco.com
> 864-236-3191
>
> -----Original Message-----
> From: Andre Lorbach [mailto:alorbach at ro1.adiscon.com] 
> Sent: Friday, April 28, 2006 9:57 AM
> To: cod at icculus.org
> Subject: RE: [cod] server log (has to be a bug)
>
> Found this today by searching in my mailarchiv!
> Thanks for the workaround :)!
>
> Any update on fixing this issue? Lots of logdata gets crapped and
> useless by this issue for logfile analysis.
>
> --
> deltaray
>
>   
>> -----Original Message-----
>> From: Henri Mecklin // Coixi [mailto:coixi at pelikaista.net]
>> Sent: Saturday, April 15, 2006 2:01 PM
>> To: cod at icculus.org
>> Subject: Re: [cod] server log (has to be a bug)
>>
>> 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.
>>>>>
>>>>>
>>>>>           
>>>       
>
>
>
>
>