On 01/14/2014 12:59 PM, Mark Morgan Lloyd wrote:
They'll get a TERM first, and five seconds later a KILL. You don't
want to restart after that first signal, because if you wait until the
second one you risk leaving files etc. associated with the program in
an indeterminate state. I've had Qemu break a database inside NTFS by
refusing to honour a shutdown.
So you can't restart after a KILL, shouldn't after a TERM, might not
want to after an INT (which, as we were discussing a few days ago,
includes ^C from the keyboard) but probably do want to restart after a
HUP. At the very least, you need to make sure that your program
propagates why it's stopped to whatever's started it.
Thanks a lot. I'll do some tests.....
-Michael
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
