We notice that our customers are trying to increase the sys_ticrate of our hlds servers at outragous numbers (something like 2000), for whatever community nonsene reasons that are floating around atm. ( i dont want get into that sort of discussion) This results in "jumpy" FPS on the hlds itself AND all other servers on the same machine, our servers for example are configured to keep a constant 500FPS wich they do until someone decides to increase their sys_ticrate to something like 2k. If someone on this machine decides to raise his sys_ticrate to lets say 2000, _ALL_ other servers on the same machine now jump from 200 to 500FPS, wich for obvious reasons is not desirable.
In the long shot the only way to avoid these problems is to lock the sys_ticrate command to the commandline args passed to the server on startup. I know that it is possible to pass it to the servers on startup (wich we do) but right now it can be overwriten by the config or simply put: rcon. Right now we are checking periodically for the actual FPS of our servers, if we find some FPS jumping we need to locate the server on the machine with his sys_ticrate set to something bogus. All of this is of course very time consuming if you consider most gsps running a high number of servers. So i request to lock the var to the start param or at least that it cant be changed by rcon if set via command line, im sure all GSPs will agree on this. regards Meth0d _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
