I strongly recommend doing more than just a system call. At the very least, check against the game running already, and if it is abort the command. You could do even better by adding this to the startup script. Take it one step further and add a panic-exit to the script if logfile > 1000 increments. A very large number of admins out there will end up starting 2 or more processes of the startup script, and then kill them hours or days later (or the sysadmins will), but there are > 10000 logfiles created by that time, which must be iterated through in the startup process.... bah
Check for the game running, and save yourself and others some heartache later.
|