There is another way without stressing the master servers: - run the server with screen - each 5 minutes, capture the text from the screen to a text file (it's an option of screen) - parse the text file for the update message, if message present, restart the screen
As you said, the master servers are already heavily overloaded, that's why Valve brought up 15 master servers for srcds games. It's not a good idea to stress it even more. >I know of maybe 6 people that use this script, so I dont think its an > issue. Besides, if you're using an update daemon, it reregisters itself > every few seconds, so deregistering has no useful effect. The script has > to use a 3-in-a-row approach the responses are so unreliable from the > master server anyway - half the time the deregister packet would never > arrive. > > A slightly better way is to increase a srcds instance's heartbeat > frequency to every few minutes, then hooking the out of date > notification there. Still much slower and requires a plugin, but doesn't > load the master server as much. If valve just put up a simple txt file > that held the lastest repo information (and was updated live from the > content servers so it wasn't made useless by delay) it would make > everyone's life a little easier. > > - Neph > > On 12/15/2009 12:34 AM, Ronny Schedel wrote: >> You should send also a quit command to the master server in your >> srcupdatecheck, otherwise thousands of non existent servers are >> registered >> to the master server if alot of people will use this script. >> >> >> >>> The latest version of nemrun: >>> http://nephyrin.net/tools/nemrun/ >>> >>> Supports starting an 'update daemon' that watches for updates and sends >>> reboot commands to servers. My servers usually are updated within >>> minutes of an update (and they beat the rush to the content servers, so >>> the DL doesn't take ages). I know its not exactly what you're looking >>> for, but its another option. You can modify the reboot command it sends >>> to servers, so you could write a plugin that provides, say, a >>> "sm_updateavailable" command that nemrun's daemon could send, allowing >>> the plugin to then decide what to do. >>> >>> There's also a way a SM could hook the 'out of date' notification, but i >>> dont know if anyone has done it in a publicly available extension. This >>> could be used in conjunction with higher heartbeat frequency to let >>> servers become aware of updates much more quickly, and decide what to >>> do. >>> >>> - Neph >>> >>> On 12/13/2009 01:44 AM, Nathan D. wrote: >>> >>>> Currently, when auto-update is turned on and updates to a game are >>>> released, we have to manually restart our server(s) so that auto-update >>>> will update the server during start up. Because we have to manually >>>> restart, there is X amount of time before our server(s) are updated and >>>> are usually empty since most of the clients have already updated. >>>> >>>> A suggestion of mine would be to make auto-update 1.) aware when >>>> updates >>>> are released and 2.) know when the server has players in it or not. >>>> Therefore, when auto-update knows there is an update available and >>>> realizes the server is empty, it could automatically issue the "exit" >>>> command to restart the server so that auto-update will run. >>>> >>>> In the meantime while Valve considers my suggestion, does anyone know >>>> some sort of practical way to have the server restart itself when an >>>> update is available? For someone who runs many servers, it is a slight >>>> hassle to restart each server manually so that auto-update can run. >>>> >>>> My apologies if something relative to this has already been discussed; >>>> I >>>> just re-joined the mailing list after many years of being unsubscribed. >>>> >>>> -Nate >>>> >>>> _______________________________________________ >>>> To unsubscribe, edit your list preferences, or view the list archives, >>>> please visit: >>>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >>>> >>>> >>> >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> please visit: >>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >>> >>> >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
