[cod] cfg files

[Jay Vasallo]

wow..this creating a config_mp_server.cfg is all new to me. I am not 
understanding why this is being done at all. Can someone please explain to 
me why you are taking the time to create a config that is generated 
automatically by the server.



----- Original Message ----- 
From: "Josh Berry" <games at chickenmonkey.co.uk>
To: <cod at icculus.org>
Sent: Tuesday, November 09, 2004 5:15 PM
Subject: Re: [cod] cfg files


> You can avoid the problem by creating a blank config_mp_server.cfg file 
> where
> the server would create it:
>
> touch config_mp_server.cfg
>
> and then change the permissions so the server cannot overwrite it
>
> chmod 000 config_mp_server.cfg
> or
> chown anotheruser:anothergroup  config_mp_server.cfg
>
> Josh
>
> On Monday 08 November 2004 20:23, stalvi wrote:
>> Ok, while testing the other suggestions that many of you sent to me I
>> stumbled upon something that might be the problem.
>>
>> my command to run the server is:
>>
>> ./cod_lnxded +set dedicated 2 +set sv_punkbuster 1 +set fs_homepath
>> "/usr/local/games/cod/" +exec bear.cfg &
>>
>>
>> What I am finding is that when it generates the config_mp_server.cfg
>> file it has these lines:
>>
>> // generated by Call of Duty, do not modify
>>
>> seta scr_motd "your MOTD here"
>> seta sv_hostname "your name here"
>>
>>
>> Even though I've set those in the bear.cfg file.
>>
>>
>> I notice when it launches, it tries to exec several other cfg files
>> which it is unable to locate.  I just assumed that as long as it found
>> one of them, it was ok.
>>
>> The way I have this exec'ing is:
>>
>> bear.cfg -> sd_map.cfg
>>
>>
>> I'm not sure where config_mp_server.cfg comes in, but do know that it
>> is auto-generated.
>