tag:blogger.com,1999:blog-6412421647806324225.post1052986482897128729..comments2024-03-07T09:56:11.326-05:00Comments on Innovate: Clarification on SIGKILL, SIGTERM, SIGINT, SIGQUIT, SIGSTP and SIGHUPProgrammergamerhttp://www.blogger.com/profile/10837024763607943216noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-6412421647806324225.post-83597302955153101762016-11-20T06:56:54.949-05:002016-11-20T06:56:54.949-05:00Hello :) very interesting article, thank you :). O...Hello :) very interesting article, thank you :). One small correction: SIGSTP cannot be handled, ignored or blocked, just like SIGKILL.Anonymoushttps://www.blogger.com/profile/13782348357739517342noreply@blogger.comtag:blogger.com,1999:blog-6412421647806324225.post-32685183273196861722014-03-20T14:48:35.968-04:002014-03-20T14:48:35.968-04:00thumb up!thumb up!yeti900513https://www.blogger.com/profile/06491083671540974927noreply@blogger.comtag:blogger.com,1999:blog-6412421647806324225.post-24137028002476320122013-10-12T16:51:31.355-04:002013-10-12T16:51:31.355-04:00Thanks for the comment and information unixguy. I ...Thanks for the comment and information unixguy. I have corrected the post.Programmergamerhttps://www.blogger.com/profile/10837024763607943216noreply@blogger.comtag:blogger.com,1999:blog-6412421647806324225.post-7760538472303693812013-09-27T13:51:24.835-04:002013-09-27T13:51:24.835-04:00No, Lee is correct, SIGQUIT is generated by Ctrl-B...No, Lee is correct, SIGQUIT is generated by Ctrl-Backslash (Ctrl+\) and on unix the default behavior for SIGQUIT is a coredump. So the OP as it currently reads saying SIGQUIT is generated by Ctrl-D is wrong.<br /><br />Empirical proof: Try running 'sleep 300' and then hit Ctrl-\, on the terminal you'll see:<br />^\Quit (core dumped)<br />Same results on linux, freebsd, etc. Note it says "Quit".<br />Also, look at the output of 'stty -a', and you should see quit = ^\.<br />And the man page for stty should say 'quit' is the quit signal.<br /><br />Try doing the same test with sleep and hitting ^D; nothing will happen. It does not generate a signal. ^D is an EOF for programs reading stdin.. functions reading stdin will return an EOF error when it's encountered, which is why hitting ^D to 'cat' will end it only if it's reading stdin. If it's reading some other device, ^D has no effect.unixguyhttps://www.blogger.com/profile/16080376538044726883noreply@blogger.comtag:blogger.com,1999:blog-6412421647806324225.post-76413848278997211962013-07-22T10:37:30.809-04:002013-07-22T10:37:30.809-04:00Yes, you are correct about SIGKILL and "kill ...Yes, you are correct about SIGKILL and "kill -9" command. However, i still think that Ctrl+D generates SIGQUIT.Programmergamerhttps://www.blogger.com/profile/10837024763607943216noreply@blogger.comtag:blogger.com,1999:blog-6412421647806324225.post-80079377787585406512013-07-05T15:57:04.863-04:002013-07-05T15:57:04.863-04:00Nitpicks:
"SIGKILL: Terminates a process imm...Nitpicks:<br /><br />"SIGKILL: Terminates a process immediately. This signal cannot be handled (caught), ignored or blocked. (The kill command in linux generates the same signal)."<br /><br />Actually, if you don't specify a signal number, the kill command will send SIGTERM, not SIGKILL. That's why you have to say "kill -9" to send SIGKILL. Of course you can specify any signal number to send with the kill command.<br /><br />"SIGQUIT: ... This is the signal generated when a user presses Ctrl+D."<br /><br />No, that's SIGHUP, which is not on your list. SIGQUIT is generated by CTRL+\ rather than CTRL+D.<br />Lee Killoughhttps://www.blogger.com/profile/07314728289631647757noreply@blogger.com