[cod] logs folder in .callofduty2/main

Henri Mecklin // Coixi coixi at pelikaista.net
Fri Apr 14 11:49:25 EDT 2006


Ok, it does happen in both servers. I did some testing and noticed that 
"logs" folder is created only in mapchange (timelimit hit, map_rotate or 
mapchange via rcon or console).

This is what i found from console_mp_server.log:

dvar set g_log logs/00000037.log

Then i found this from config_mp_server.cfg

g_log logs/00000037.log

It seems that server writes automatically g_log logs/000000<X>.log to 
config_mp_server.cfg and server execes it in mapchange and log is changed.

I bet it can be bypassed by setting config_mp_server.cfg read only.

 - Coixi


Henri Mecklin // Coixi wrote:
> Tested with 100% same configs, iwd files etc but 2nd server still 
> makes the logs folder.
>
> Very very strange, need to reboot/change map with rcon in 1st server 
> like i did in 2nd.
>
> - Coixi
>
> Ian mu wrote:
>> Ah sorry misread, thought you meant from same install. Does sound odd 
>> then assuming no one else has changed some config. (Is it possible 
>> someone changed a log setting via rcon and seta and its saved in the 
>> config_mp_server.cfg ?). Interesting if the corrupt pak would do that 
>> though.
>>  
>> md5sum iw_15.iwd
>> 9edc75cbe32d571065a15621ba441903  iw_15.iwd
>>  
>> Hope that helps at least :).
>>
>>
>>  
>> On 4/14/06, *Henri Mecklin // Coixi* <coixi at pelikaista.net 
>> <mailto:coixi at pelikaista.net>> wrote:
>>
>>     Yeah, i know and i'm attending to use it even in single server 
>> but in
>>     these, these two are completely different machines.
>>
>>     The problem may have been with my iw_15.iwd file which was
>>     corrupted (ar
>>     atleast it had different md5sum than iw_15.iwd file in my 1st 
>> server).
>>     I'm gonna run tests now with the right iw_15.iwd file :)
>>
>>     Can you verify that md5sum for iw_15.iwd is:
>>
>>     9edc75cbe32d571065a15621ba441903
>>
>>     Thanks
>>
>>     - Coixi
>>
>>     Ian mu wrote:
>>     > Hiya, for multiple servers I'd tend you use +set fs_homepath
>>     > <somepath> for configs and logs. Not really sure its ideal 
>> having 2
>>     > processes trying to write to the same logfile etc. Not sure
>>     thats the
>>     > actual problem you are mentioning anyway, but its the way I'd 
>> start
>>     > off with when having more than 1 server.
>>     >
>>     > On 4/14/06, *Henri Mecklin // Coixi* < coixi at pelikaista.net
>>     <mailto:coixi at pelikaista.net>
>>     > <mailto:coixi at pelikaista.net <mailto:coixi at pelikaista.net>>> 
>> wrote:
>>     >
>>     >     Hi,
>>     >
>>     >     I'm running two linux servers, both with 1.2a binaries. Both
>>     are using
>>     >     same commindline arguments in startup:
>>     >
>>     >     cod2_lnxded +set sv_punkbuster 1 +exec server.cfg +set +set
>>     g_log
>>     >     "games_mp.log" +set g_logSync "1" +set logfile "1" +map_rotate
>>     >
>>     >     Both servers are running the same configuration and same mods
>>     >     (shellshock removal and nofog). The weird thing is that soon
>>     after the
>>     >     server start, my second server creates a "logs" dir into
>>     >     .callofduty2/main folder (fs_homepath / profilefolder) and 
>> adds
>>     >     000000<random_number>.log file in there. The logfile
>>     contains basic
>>     >     games_mp.log info, joins, quits, kills, etc.
>>     >
>>     >     I really have no idea why the 1st server doesn't that but
>>     2nd does.
>>     >
>>     >     Specifications of the servers:
>>     >
>>     >     Server 1:
>>     >     - P4 2,8GHz
>>     >     - Linux version 2.6.8-1-k7 , gcc 3.3.4 (Debian)
>>     >
>>     >     Server 2:
>>     >     - AMD Sempron 2800+
>>     >     - Linux version 2.6.8-1-k7, gcc 3.3.4 (Debian)
>>     >
>>     >     I am aware that one of my friend has this problem aswell
>>     (problem
>>     >     because i haven't heard about his nor wanna use this
>>     'feature'). Have
>>     >     you discovered samekinda problem my fellow admins? :)
>>     >
>>     >     - Coixi
>>     >
>>     >
>>     >
>>     >
>>     >
>>     >
>>
>>
>



More information about the Cod mailing list