Does a disowned process receive signals other than SIGHUP?












1















  • Is it correct that a shell can send signals only to its jobs, but can't send signals to processes which are not its jobs?


  • disown moves a job out of the job list of a shell. Does that mean a disowned process will not receive all the signals (not just SIGHUP) from its parent shell? If it will still receives other signals, why so?











share|improve this question



























    1















    • Is it correct that a shell can send signals only to its jobs, but can't send signals to processes which are not its jobs?


    • disown moves a job out of the job list of a shell. Does that mean a disowned process will not receive all the signals (not just SIGHUP) from its parent shell? If it will still receives other signals, why so?











    share|improve this question

























      1












      1








      1








      • Is it correct that a shell can send signals only to its jobs, but can't send signals to processes which are not its jobs?


      • disown moves a job out of the job list of a shell. Does that mean a disowned process will not receive all the signals (not just SIGHUP) from its parent shell? If it will still receives other signals, why so?











      share|improve this question














      • Is it correct that a shell can send signals only to its jobs, but can't send signals to processes which are not its jobs?


      • disown moves a job out of the job list of a shell. Does that mean a disowned process will not receive all the signals (not just SIGHUP) from its parent shell? If it will still receives other signals, why so?








      bash shell signals disown






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 28 '16 at 22:36









      Tim

      26.1k74246455




      26.1k74246455






















          2 Answers
          2






          active

          oldest

          votes


















          3














          You can always send signals to any process you own. The shell presumably won't on it's own.






          share|improve this answer





















          • Thanks. I forgot to say I am only talking about signals sent from the parent shell. So the shell won't send any signal to a disowned process, not just SIGHUP?
            – Tim
            Feb 28 '16 at 23:28





















          1














          Easy to test:



          sleep will die if it receives SIGUSR1:



          $ sleep 999 &
          [1] 7399
          $ kill -USR1 7399
          $
          [1]+ User defined signal 1 sleep 999


          So let's disown it and see if it survives:



          $ sleep 999 &
          [1] 7396
          $ disown %1
          $ jobs
          $ ps -fp 7396
          UID PID PPID C STIME TTY TIME CMD
          schaller 7396 7360 0 19:59 pts/0 00:00:00 sleep 999
          $ kill -USR1 7396
          $ ps -fp 7396
          UID PID PPID C STIME TTY TIME CMD
          $





          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f266396%2fdoes-a-disowned-process-receive-signals-other-than-sighup%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            You can always send signals to any process you own. The shell presumably won't on it's own.






            share|improve this answer





















            • Thanks. I forgot to say I am only talking about signals sent from the parent shell. So the shell won't send any signal to a disowned process, not just SIGHUP?
              – Tim
              Feb 28 '16 at 23:28


















            3














            You can always send signals to any process you own. The shell presumably won't on it's own.






            share|improve this answer





















            • Thanks. I forgot to say I am only talking about signals sent from the parent shell. So the shell won't send any signal to a disowned process, not just SIGHUP?
              – Tim
              Feb 28 '16 at 23:28
















            3












            3








            3






            You can always send signals to any process you own. The shell presumably won't on it's own.






            share|improve this answer












            You can always send signals to any process you own. The shell presumably won't on it's own.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Feb 28 '16 at 23:16









            vonbrand

            14.1k22644




            14.1k22644












            • Thanks. I forgot to say I am only talking about signals sent from the parent shell. So the shell won't send any signal to a disowned process, not just SIGHUP?
              – Tim
              Feb 28 '16 at 23:28




















            • Thanks. I forgot to say I am only talking about signals sent from the parent shell. So the shell won't send any signal to a disowned process, not just SIGHUP?
              – Tim
              Feb 28 '16 at 23:28


















            Thanks. I forgot to say I am only talking about signals sent from the parent shell. So the shell won't send any signal to a disowned process, not just SIGHUP?
            – Tim
            Feb 28 '16 at 23:28






            Thanks. I forgot to say I am only talking about signals sent from the parent shell. So the shell won't send any signal to a disowned process, not just SIGHUP?
            – Tim
            Feb 28 '16 at 23:28















            1














            Easy to test:



            sleep will die if it receives SIGUSR1:



            $ sleep 999 &
            [1] 7399
            $ kill -USR1 7399
            $
            [1]+ User defined signal 1 sleep 999


            So let's disown it and see if it survives:



            $ sleep 999 &
            [1] 7396
            $ disown %1
            $ jobs
            $ ps -fp 7396
            UID PID PPID C STIME TTY TIME CMD
            schaller 7396 7360 0 19:59 pts/0 00:00:00 sleep 999
            $ kill -USR1 7396
            $ ps -fp 7396
            UID PID PPID C STIME TTY TIME CMD
            $





            share|improve this answer


























              1














              Easy to test:



              sleep will die if it receives SIGUSR1:



              $ sleep 999 &
              [1] 7399
              $ kill -USR1 7399
              $
              [1]+ User defined signal 1 sleep 999


              So let's disown it and see if it survives:



              $ sleep 999 &
              [1] 7396
              $ disown %1
              $ jobs
              $ ps -fp 7396
              UID PID PPID C STIME TTY TIME CMD
              schaller 7396 7360 0 19:59 pts/0 00:00:00 sleep 999
              $ kill -USR1 7396
              $ ps -fp 7396
              UID PID PPID C STIME TTY TIME CMD
              $





              share|improve this answer
























                1












                1








                1






                Easy to test:



                sleep will die if it receives SIGUSR1:



                $ sleep 999 &
                [1] 7399
                $ kill -USR1 7399
                $
                [1]+ User defined signal 1 sleep 999


                So let's disown it and see if it survives:



                $ sleep 999 &
                [1] 7396
                $ disown %1
                $ jobs
                $ ps -fp 7396
                UID PID PPID C STIME TTY TIME CMD
                schaller 7396 7360 0 19:59 pts/0 00:00:00 sleep 999
                $ kill -USR1 7396
                $ ps -fp 7396
                UID PID PPID C STIME TTY TIME CMD
                $





                share|improve this answer












                Easy to test:



                sleep will die if it receives SIGUSR1:



                $ sleep 999 &
                [1] 7399
                $ kill -USR1 7399
                $
                [1]+ User defined signal 1 sleep 999


                So let's disown it and see if it survives:



                $ sleep 999 &
                [1] 7396
                $ disown %1
                $ jobs
                $ ps -fp 7396
                UID PID PPID C STIME TTY TIME CMD
                schaller 7396 7360 0 19:59 pts/0 00:00:00 sleep 999
                $ kill -USR1 7396
                $ ps -fp 7396
                UID PID PPID C STIME TTY TIME CMD
                $






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 6 hours ago









                Jeff Schaller

                38.9k1053125




                38.9k1053125






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f266396%2fdoes-a-disowned-process-receive-signals-other-than-sighup%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    CARDNET

                    Boot-repair Failure: Unable to locate package grub-common:i386

                    濃尾地震