[cod] Forcing server-side variables on a cod2 server

[Morpheus]

It is almost completely my case : as a reward for an online 1-night cup 
that we organize for small teams, we "offer" a year (or so, I'm not 
organizing it, just putting the technics in place) of a private server, 
that has to be fixed-sized, and private.

I have already thought about a script to monitor and if possible restore 
the settings I want to keep. But I don't find it very clean (because 
it's external).

Le 06/03/2010 21:09, Joachim Sehlstedt a écrit :
> You don't get what he is saying. He want to force a g_password all the 
> time so not a person renting the server can rcon in and make it 
> public. I would also be interested in this as well. Right now I have a 
> script that checks our server each minute and shuts the server down 
> and send out a mail warning the renter if it detects that someone 
> changed the max players or removed the password.
>
> In hlds you used to be able to do things like: sv_password "pass"; 
> alias sv_password "wait"
>
> On 2010-03-06 20:59, Kovács Dániel wrote:
>> So, you want the server to use g_password anytime?
>> If so: I think you should add +set g_password , i guess it should work
>> if not: I you write g_password in the server's cfg, later you can 
>> make the
>> server public from Rcon.
>>
>>
>>
>> Kovács Dániel
>> info at kovacsdaniel.hu
>>
>>
>> -----Eredeti üzenet-----
>> Feladó: Morpheus [mailto:morpheus at clantoc.org]
>> Küldve: Saturday, March 06, 2010 8:49 PM
>> Címzett: Call of Duty server admin list.
>> Tárgy: Re: [cod] Forcing server-side variables on a cod2 server
>>
>> I already use screen to start all my game servers : I have 3 cod2, 1
>> cod4, and 1 cod5 running this way. It's not a problem to set variables,
>> but to keep the setting during the uptime.
>>
>> What I want, for, say, the password thing, is that you can't make your
>> server "public" by RCon using the 'g_password "" ' command. The same
>> applies to sv_maxplayers setting.
>>
>> I have an idea to send rcon command with a php script by cron, but if a
>> more elegant way (built-in) to do it, I prefer that.
>>
>> Sorry for not being very clear, I'm quite tired these days, and english
>> is not my native language.
>>
>> Le 06/03/2010 20:35, Kovács Dániel a écrit :
>>> Hi!
>>> In Debian, I created a file called started or anything else, then you
>> should
>>> write it in:
>>> ./cod2_lnxded +set g_password "" +set  etc..
>>> If you are done, you should chmod the file to run it, then run.
>>> On the other hand, if I were you, I would use screen (to install: 
>>> apt-get
>>> install screen)
>>> so, you can start more servers, and you only have to modify your 
>>> starter
>>> file :
>>> screen -A -m -d -S cod2 ./cod2_lnxded ...
>>>
>>> Daniel
>>>
>>> Kovács Dániel
>>> info at kovacsdaniel.hu
>>>
>>> -----Eredeti üzenet-----
>>> Feladó: Morpheus [mailto:morpheus at clantoc.org]
>>> Küldve: Saturday, March 06, 2010 8:26 PM
>>> Címzett: Call of Duty server admin list.
>>> Tárgy: [cod] Forcing server-side variables on a cod2 server
>>>
>>> Hi guys,
>>>
>>> I would like to force some server-side variables to keep their initial
>>> values. For example, on a cod2 server you can modify maxplayers through
>>> RCon.
>>>
>>> I need to prevent maxplayers modification through RCon, and also make
>>> the "g_password" mandatory. For this one, I already have seen a server
>>> "locked" even if g_password is set to "", so I know it's possible for
>>> this setting. But I'm not sure about maxplayers.
>>>
>>> I don't have had much success sniffing on google to find information
>>> (all password related results are for RCon or g_password...), so I'm
>>> looking toward the specialists :P
>>>
>>> Does anyone have the way to go ?
>>>
>>> Thx in advance.
>>>
>>> Morpheus
>>> _______________________________________________
>>> cod mailing list
>>> cod at icculus.org
>>> http://icculus.org/mailman/listinfo/cod
>>>
>>> _______________________________________________
>>> cod mailing list
>>> cod at icculus.org
>>> http://icculus.org/mailman/listinfo/cod
>>>
>> _______________________________________________
>> cod mailing list
>> cod at icculus.org
>> http://icculus.org/mailman/listinfo/cod
>>
>> _______________________________________________
>> cod mailing list
>> cod at icculus.org
>> http://icculus.org/mailman/listinfo/cod
>>
> _______________________________________________
> cod mailing list
> cod at icculus.org
> http://icculus.org/mailman/listinfo/cod