Quote:
Originally Posted by
jackliang
yes, then what is the defaut behavior in detail of threse signals?
Unless otherwise handled? Gracelessly kill the program. A very few signals have special hardwired behavior, like SIGSTOP and SIGCONT, but these trigger behavior that happens
outside the program and are uncatchable. And no, before you ask a third time, none of them are for flushing the queues(which happens in userspace anyway).
If you want a special "flush the queues" signal you have to make it yourself. Better yet, fix your application so that it catches SIGTERM properly and quits gracefully instead of having to be killed hard.