The sysadmin would still have to initiate the bash script since he can access the "games" user.
I use a stop_css script on my server that looks like this: /usr/bin/screen -r css -X quit "css" is the name assigned to the screen instance. This causes the server program to exit gracefully but also closes the screen instance. It would still require admin privileges to start back up. ......Chuck Suse 9.0-64 >> Yeah, but those solutions require his sysadmin to get off his lazy butt and grant him privileges. (Or it could just be that the sysadmin has a strict security policy). Running a bash instance inside screen takes no additional pain on the part of either of them. -John Sheu On Tue, 2005-11-01 at 09:13 +0100, Regime wrote: > Alternitively, get him to look into "sudo" and grant you permission to > "sudo" all or some commands as the games user. Type in "man sudo" for > more information. > > >> The servers are running on screens, but not under my user > >>account - they're running on a 'games' user. If I were to kill the screen, I > >>wouldn't be able to create a new screen under the 'games' user since I don't > >>have the privileges to do so. > >> > > _______________________________________________ > 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: << _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
