[cod] start/stop script

[escapedturkey]

I still think it's too risky to allow a process to possibly kill itself 
rather than just terminate it via kill -9 -1. Duplicate processes are 
much worse. :)

Christian Gerbrandt wrote:
> 'kill -9' should be the last resort.
> You are sending a SIGKILL to the process id, which will prevent any cleanup
> operations from the process.
> All in-kernel operations are killed, which could lead to data corruption.
> You should only use 'kill -9' if no other kill signal has been successfull.
> 
> -----Original Message-----
> From: escapedturkey [mailto:escapedturkey at escapedturkey.com] 
> Sent: 13 December 2009 13:08
> To: Call of Duty server admin list.
> Subject: Re: [cod] start/stop script
> 
>  From my understanding -9 makes sure the process is killed vs. just hanging
> around. If you allow the process to kill itself cleanly, it may just hang
> and you can end up with multiple dead processes -- that is my experience.
> 
> Jarkko Mäntylä wrote:
>> On 10.12.2009 08:36, escapedturkey wrote:
>>> Which ideas? The kill -9 -1?
>>>
>>> If he's running the game server as a user (in usermin) the kill -9 -1 
>>> is perfect for clean-up, otherwise you'll have multiple processes 
>>> running every-time you start the game server. Did I miss something?
>>>
>>> Also, the original poster of this thread and I know each other. :)
>>>
>> Using SIGKILL (-9) prevents any process to do any clean-up, you only 
>> use it with broken programs. If the user is only running gameservers 
>> that all need to be stopped at the same time then using -1 group might 
>> be good idea.
>> _______________________________________________
>> cod mailing list
>> cod at icculus.org
>> http://icculus.org/mailman/listinfo/cod
>>
> _______________________________________________
> cod mailing list
> cod at icculus.org
> http://icculus.org/mailman/listinfo/cod
> 
> 
> 
> _______________________________________________
> cod mailing list
> cod at icculus.org
> http://icculus.org/mailman/listinfo/cod
>