On Sunday March 21 2010, Tejas Guruswamy wrote:
On 21/03/10 11:56, arygroup@gmail.com wrote:
...
So there is no way to make what I want in a legal way if I'm not sure how all the programs in my list handle the signals, right?
It's completely legal, just a question of whether the application author did their job well and considered the needs of command-line users. SIGTERM (the default signal from kill) is simply "asking" the program to quit, so a well-written program should have plenty of time to save config etc. and shutdown cleanly. So there should be no danger to sending SIGKILL or SIGHUP to a well-written program.
Just to be clear, no process may catch SIGKILL, so any program that requires shut-down processing (say, to ensure the integrity of any files they use) may corrupt that external data if stopped using SIGKILL.
In fact the normal logout/shutdown process involves sending SIGTERM to all processes. On the other hand SIGKILL (kill -9) is an immediate end to the program.
...
Regards, Tejas
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org