Re: Process Signal Bug On Intel Dual Core Machines?
site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Aug 31, 2006, at 2:58 AM, Markus Hanauska wrote: It could be that SIGQUIT is being ignored; if the signal is ignored it will be silently discarded rather than appear in the blocked or pending signal lists. I'd tell you to use "ps -O ignored," which is documented but apparently doesn't actually work: $ ps -O ignored ps: sigignore: keyword not found William Kucharski kucharsk@mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... It also does not explain why SIGQUIT won't work (it is not blocked, I made my app print out the whole signal mask and SIGQUIT is not blocked), but since we don't use it anyway, this might be an entirely different bug and should maybe be ignored for this issues. so the next easiest thing would be to use sigaction(2) to get the previous disposition of SIGQUIT for your daemon and check to see if its handler is set to SIG_IGN. This email sent to site_archiver@lists.apple.com
participants (1)
-
William Kucharski