rwald wrote:Actually, my thoughts went something like this: "If he just hit ctrl+c once, it would send SIGINT; that would give the autoconfig process time to exit cleanly, which would probably notify field agents to release the children. However, by sending it twice, he might have interrupted that cleanup process and prevented the 'release children' command from being sent."
Incidentally, I'm not sure how this relates to possibly sending SIGKILL; I know that, for example, rsync will clean up nicely if sent SIGTERM but will leave temporary files when sent SIGKILL. I don't know if sending it SIGINT quickly in rapid succession does anything interesting, though.
Ctrl-C always send SIGTERM no matter how many times you press it. Also when the signal is handled generally the OS will release the handler, until you set it back again. This is to protect against program going crazy when it receives a signal while processing another one. Though, if you really want it you can make your program go crazy.