tee: What exactly does “--ignore-interrupts” option do?











up vote
6
down vote

favorite
3












The title basically says it all. tee has an option --ignore-interrupts:



-i, --ignore-interrupts   ignore interrupt signals


Can anyone explain/give an example in which situation this is important? Thanks!










share|improve this question


























    up vote
    6
    down vote

    favorite
    3












    The title basically says it all. tee has an option --ignore-interrupts:



    -i, --ignore-interrupts   ignore interrupt signals


    Can anyone explain/give an example in which situation this is important? Thanks!










    share|improve this question
























      up vote
      6
      down vote

      favorite
      3









      up vote
      6
      down vote

      favorite
      3






      3





      The title basically says it all. tee has an option --ignore-interrupts:



      -i, --ignore-interrupts   ignore interrupt signals


      Can anyone explain/give an example in which situation this is important? Thanks!










      share|improve this question













      The title basically says it all. tee has an option --ignore-interrupts:



      -i, --ignore-interrupts   ignore interrupt signals


      Can anyone explain/give an example in which situation this is important? Thanks!







      linux tee






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 4 '14 at 14:42









      alexander.biskop

      1335




      1335






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          9
          down vote



          accepted










          When called with -i, tee ignores the interrupt signal (SIGINT), which is normally issued by your terminal when hitting Ctrl+C.






          share|improve this answer





















          • And in which situation this is important?
            – hakre
            Jul 4 '14 at 13:01






          • 6




            If you're using tee in a command line pipe like some long running command | tee output, this might be helpful if you want to kill the input provider with Ctrl+C, but want tee to exit gracefully (by reading EOF from the pipe).
            – Andreas Wiese
            Jul 4 '14 at 13:46












          • Ah, very useful and a nice description, I was a little irritated. Now I'll add it to some of my scripts. Thanks!
            – hakre
            Jul 4 '14 at 15:12










          • @AndreasWiese: You should add your comment to your answer.
            – Zaz
            Feb 6 '17 at 20:16


















          up vote
          0
          down vote













          If tee is used with -i, --ignore-interrupts options, It wont accept any interrupt signals like CNTRL+C ^C or Kill signals Except signal KILL or Signal Terminate.






          share|improve this answer

















          • 1




            That's not quite right; tee does exactly what the option states and only ignores SIGINT. All other signals are delivered as without -i.
            – Andreas Wiese
            Apr 4 '14 at 16:17













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          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',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2fsuperuser.com%2fquestions%2f737715%2ftee-what-exactly-does-ignore-interrupts-option-do%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








          up vote
          9
          down vote



          accepted










          When called with -i, tee ignores the interrupt signal (SIGINT), which is normally issued by your terminal when hitting Ctrl+C.






          share|improve this answer





















          • And in which situation this is important?
            – hakre
            Jul 4 '14 at 13:01






          • 6




            If you're using tee in a command line pipe like some long running command | tee output, this might be helpful if you want to kill the input provider with Ctrl+C, but want tee to exit gracefully (by reading EOF from the pipe).
            – Andreas Wiese
            Jul 4 '14 at 13:46












          • Ah, very useful and a nice description, I was a little irritated. Now I'll add it to some of my scripts. Thanks!
            – hakre
            Jul 4 '14 at 15:12










          • @AndreasWiese: You should add your comment to your answer.
            – Zaz
            Feb 6 '17 at 20:16















          up vote
          9
          down vote



          accepted










          When called with -i, tee ignores the interrupt signal (SIGINT), which is normally issued by your terminal when hitting Ctrl+C.






          share|improve this answer





















          • And in which situation this is important?
            – hakre
            Jul 4 '14 at 13:01






          • 6




            If you're using tee in a command line pipe like some long running command | tee output, this might be helpful if you want to kill the input provider with Ctrl+C, but want tee to exit gracefully (by reading EOF from the pipe).
            – Andreas Wiese
            Jul 4 '14 at 13:46












          • Ah, very useful and a nice description, I was a little irritated. Now I'll add it to some of my scripts. Thanks!
            – hakre
            Jul 4 '14 at 15:12










          • @AndreasWiese: You should add your comment to your answer.
            – Zaz
            Feb 6 '17 at 20:16













          up vote
          9
          down vote



          accepted







          up vote
          9
          down vote



          accepted






          When called with -i, tee ignores the interrupt signal (SIGINT), which is normally issued by your terminal when hitting Ctrl+C.






          share|improve this answer












          When called with -i, tee ignores the interrupt signal (SIGINT), which is normally issued by your terminal when hitting Ctrl+C.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 4 '14 at 16:16









          Andreas Wiese

          1,771711




          1,771711












          • And in which situation this is important?
            – hakre
            Jul 4 '14 at 13:01






          • 6




            If you're using tee in a command line pipe like some long running command | tee output, this might be helpful if you want to kill the input provider with Ctrl+C, but want tee to exit gracefully (by reading EOF from the pipe).
            – Andreas Wiese
            Jul 4 '14 at 13:46












          • Ah, very useful and a nice description, I was a little irritated. Now I'll add it to some of my scripts. Thanks!
            – hakre
            Jul 4 '14 at 15:12










          • @AndreasWiese: You should add your comment to your answer.
            – Zaz
            Feb 6 '17 at 20:16


















          • And in which situation this is important?
            – hakre
            Jul 4 '14 at 13:01






          • 6




            If you're using tee in a command line pipe like some long running command | tee output, this might be helpful if you want to kill the input provider with Ctrl+C, but want tee to exit gracefully (by reading EOF from the pipe).
            – Andreas Wiese
            Jul 4 '14 at 13:46












          • Ah, very useful and a nice description, I was a little irritated. Now I'll add it to some of my scripts. Thanks!
            – hakre
            Jul 4 '14 at 15:12










          • @AndreasWiese: You should add your comment to your answer.
            – Zaz
            Feb 6 '17 at 20:16
















          And in which situation this is important?
          – hakre
          Jul 4 '14 at 13:01




          And in which situation this is important?
          – hakre
          Jul 4 '14 at 13:01




          6




          6




          If you're using tee in a command line pipe like some long running command | tee output, this might be helpful if you want to kill the input provider with Ctrl+C, but want tee to exit gracefully (by reading EOF from the pipe).
          – Andreas Wiese
          Jul 4 '14 at 13:46






          If you're using tee in a command line pipe like some long running command | tee output, this might be helpful if you want to kill the input provider with Ctrl+C, but want tee to exit gracefully (by reading EOF from the pipe).
          – Andreas Wiese
          Jul 4 '14 at 13:46














          Ah, very useful and a nice description, I was a little irritated. Now I'll add it to some of my scripts. Thanks!
          – hakre
          Jul 4 '14 at 15:12




          Ah, very useful and a nice description, I was a little irritated. Now I'll add it to some of my scripts. Thanks!
          – hakre
          Jul 4 '14 at 15:12












          @AndreasWiese: You should add your comment to your answer.
          – Zaz
          Feb 6 '17 at 20:16




          @AndreasWiese: You should add your comment to your answer.
          – Zaz
          Feb 6 '17 at 20:16












          up vote
          0
          down vote













          If tee is used with -i, --ignore-interrupts options, It wont accept any interrupt signals like CNTRL+C ^C or Kill signals Except signal KILL or Signal Terminate.






          share|improve this answer

















          • 1




            That's not quite right; tee does exactly what the option states and only ignores SIGINT. All other signals are delivered as without -i.
            – Andreas Wiese
            Apr 4 '14 at 16:17

















          up vote
          0
          down vote













          If tee is used with -i, --ignore-interrupts options, It wont accept any interrupt signals like CNTRL+C ^C or Kill signals Except signal KILL or Signal Terminate.






          share|improve this answer

















          • 1




            That's not quite right; tee does exactly what the option states and only ignores SIGINT. All other signals are delivered as without -i.
            – Andreas Wiese
            Apr 4 '14 at 16:17















          up vote
          0
          down vote










          up vote
          0
          down vote









          If tee is used with -i, --ignore-interrupts options, It wont accept any interrupt signals like CNTRL+C ^C or Kill signals Except signal KILL or Signal Terminate.






          share|improve this answer












          If tee is used with -i, --ignore-interrupts options, It wont accept any interrupt signals like CNTRL+C ^C or Kill signals Except signal KILL or Signal Terminate.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 4 '14 at 14:50









          Vasanta Koli

          1011




          1011








          • 1




            That's not quite right; tee does exactly what the option states and only ignores SIGINT. All other signals are delivered as without -i.
            – Andreas Wiese
            Apr 4 '14 at 16:17
















          • 1




            That's not quite right; tee does exactly what the option states and only ignores SIGINT. All other signals are delivered as without -i.
            – Andreas Wiese
            Apr 4 '14 at 16:17










          1




          1




          That's not quite right; tee does exactly what the option states and only ignores SIGINT. All other signals are delivered as without -i.
          – Andreas Wiese
          Apr 4 '14 at 16:17






          That's not quite right; tee does exactly what the option states and only ignores SIGINT. All other signals are delivered as without -i.
          – Andreas Wiese
          Apr 4 '14 at 16:17




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • 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%2fsuperuser.com%2fquestions%2f737715%2ftee-what-exactly-does-ignore-interrupts-option-do%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

          AnyDesk - Fatal Program Failure

          How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

          QoS: MAC-Priority for clients behind a repeater