I'm quite positive about the optional updates - the master server out of date message means your server was denied listing for being too old - so unless valve configured something wrong for that update, it was definitely required (or required to stay listed at least).
For the notifications, the notifyadmins.sh could launch background jobs with timers, or really do whatever you want. But if you have an idea for a feature/switch I could add to nemrun to make this easier, let me know. - Neph On Mon, Aug 30, 2010 at 6:13 AM, PharaohsPaw <[email protected]> wrote: > Thanks for the replies everyone. > >> Tony is correct - optional updates are not detected at all by >> srcupdatecheck. The master server simply is not aware of them. To >> detect them would require A: A custom repository script abusing code >> deep inside hldsupdatetool (valve would not appreciate this), or B: >> Valve releasing some kind of XML feed or something with version >> information and optional update information. > >> If you wish to manually trigger an update, however, when an optional >> update is available, you can delete <gamedir>/steam.inf - which will >> cause the update daemon to trigger immediately. If you're not using an >> update daemon, just delete steam.inf and reboot a server so its update >> check fires. >> > > After reading more through srcupdatecheck it looked to me like it would > only exit with returncode 7 when a "server is out of date" message was > returned from a check. There was one update a couple weeks ago (TF2 I > think) that got applied which I thought was optional from reading the > description, it's what made me wonder if nemrun was applying optional > updates, but it must have been something else. I was using manual > deletion of the steam.inf file + -verify_all to force update checks (to > make sure I had things working correctly when an update came out) so it > was probably all my tinkering around that caused this non-required update > to be installed. > >> As for warning people about an update before it happens, the script >> runs the -notifycommand synchronously - nemrun wont continue until it >> exits. So you can throw a warning in there followed by a "sleep 60". >> Of course with -updatefirst this isn't needed. > > > True, I was really only thinking it would be sort of nice to send a couple > alerts to the game (csay,hsay,etc.) a few seconds before sending the quit > command when update was complete, so ppl on the server would know that the > reason the server was going down/rebooting was because of an update, > rather than a crash or something. Especially since the servers tend to > fill up pretty quick if yours are among the first updated and back online. > > Thanks again, > PharaohsPaw > > _______________________________________________ > 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
