Hi,
 
I would suggest two/three options that might be feasible and might work.  I'm not sure about the order of config execution and such as I left the server renting business a few years back.  This is what I would do/try:
 
1) Alter your web software to either parse the server.cfg and detect a change in this variable, or have it add a new line at the VERY end of the config when the user saves the config changes.  Of the latter of the two options here the new ticrate line should in theory overwrite any that the user adds to the config.  They will be unaware of this change provided you make the web software remove this line when it is loaded within the web software.
 
2) Add an include line (if there is such a thing, I can't really remember) that includes another config.  Call this config file something like "mycompany.cfg" and state that this line must not be removed.  Or BETTER YET, why not create this config, change the ownership of the file to root so that FTP users can't make any modifications to that file and add this config to the command line of the server startup script, this should execute after the server.cfg, therefore overwritting any previous config settings!
 
I think either of these should work, it all depends on how linux savy you are, and how much of the web software you can alter.  I believe this is easily achieveable.  Infact I just had another idea!  If you can't do ANY of the above, why not create a cron job to add a new ticrate config setting for ALL servers on a routine basis, that way when a server is restarted these new settings will take effect.  Or you can enforce it every night at a set time to check the config setting, and if it appears to be incorrect, change it and then restart the server, and send a policy violation email to the owner issuing a warning.  Further violations will result in the server cancelled without refund, etc.
 
I hope I've provided you with a viable solution or at least food for thought on this issue.  There is always a solution to a problem, you just have to find it!
 
Kind regards,
Dave.
 
 
P.S. If you continue to have problems with this issue and would like me to look into providing you with a solution, I would be happy to do so, however, unfortunately for the likes of yourself, my time costs money.  But the option is there should you require it.
----- Original Message -----
From: Terry
Sent: Thursday, December 29, 2005 6:40 PM
Subject: RE: [hlds_apps] locking variables with hlds for counter-strike

I agree with Benjamin.  Make it very clear that tickrate is not to be changed, and if any server is found with that variable changed from the default, "X" will happen.  If that still doesn't work, about the only thing you do is write a script/program to periodically get the cvars from each server and check it's value.  You could have a list of your servers to feed from that you could edit when you add/remove servers.  Heck, you could even show the result in a nice grid and if any server shows a ticrate higher than what you set, it could display in red and/or send an email.  ;-)  I wouldn't be surprised if there was already something out there that did this.
 
Terry


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ales Koprivnikar
Sent: Thursday, December 29, 2005 11:20 AM
To: hlds_apps@list.valvesoftware.com
Subject: RE: [hlds_apps] locking variables with hlds for counter-strike

Even if u have just 5 it's hell. The problem is also that they can just change it on the server and not alter the cfg files.

 

Best regards

            Ales

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Benjamin Davison
Sent: Thursday, December 29, 2005 4:29 PM
To: hlds_apps@list.valvesoftware.com
Subject: Re: [hlds_apps] locking variables with hlds for counter-strike

 

Not that I have heard of, I think the best thing to-do is just make sure that they are aware that they should not change it. And if you notice abnormal CPU usage, just check the CFG files.

Now obviously this is easy with a few amount of servers, but with a big amount of servers it's going to be hell.

On 12/29/05, Jayden Rif <[EMAIL PROTECTED]> wrote:

dunno on that one sorry all i'm doing with my hlds servers is running a few
dedicated LAN servers in my internet cafe.

Sorry

Jayden


>From: "Ales Koprivnikar" < [EMAIL PROTECTED]>
>Reply-To: hlds_apps@list.valvesoftware.com
>To: <hlds_apps@list.valvesoftware.com >
>Subject: [hlds_apps] locking variables with hlds for counter-strike
>Date: Thu, 29 Dec 2005 11:08:19 +0100
>
>Hello,
>
>I have a little problem with hlds. I am renting servers to people. They get
>ftp access to the server, a web interface restart and the ip+rcon pw. That
>means they have full control over the server. So i just need to lock the
>variable sys_ticrate to resonable value(like 200) so that 1 server wont eat
>up all the cpu. (this is ofcourse done in server.cfg but smart(!) server
>owners change this to like 10000 and that really plays tricks with the cpu
>usage).
>
>So is  there a way lock the variable in question?
>
>
>
>Ty for you answers
>
>
>
>Best Regards
>
>             Ales
>



_______________________________________________
hlds_apps mailing list
hlds_apps@list.valvesoftware.com
http://list.valvesoftware.com/mailman/listinfo/hlds_apps




--
- Benjamin Davison


No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.9/216 - Release Date: 29/12/2005
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.9/216 - Release Date: 29/12/2005

Reply via email to