tee: What exactly does “--ignore-interrupts” option do?
up vote
6
down vote
favorite
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
asked Apr 4 '14 at 14:42
alexander.biskop
1335
add a comment |
up vote
6
down vote
favorite
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
asked Apr 4 '14 at 14:42
alexander.biskop
1335
add a comment |
up vote
6
down vote
favorite
up vote
6
down vote
favorite
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
asked Apr 4 '14 at 14:42
alexander.biskop
1335
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
linux tee
asked Apr 4 '14 at 14:42
alexander.biskop
1335
asked Apr 4 '14 at 14:42
alexander.biskop
1335
asked Apr 4 '14 at 14:42
alexander.biskop
1335
asked Apr 4 '14 at 14:42
alexander.biskop
1335
asked Apr 4 '14 at 14:42
alexander.biskop
1335
1335
add a comment |
add a comment |
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.
answered Apr 4 '14 at 16:16
Andreas Wiese
1,771711
And in which situation this is important?
– hakre
Jul 4 '14 at 13:01
6
If you're usingteein a command line pipe likesome long running command | tee output, this might be helpful if you want to kill the input provider withCtrl+C, but wantteeto exit gracefully (by readingEOFfrom 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
add a comment |
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.
answered Apr 4 '14 at 14:50
Vasanta Koli
1011
1
That's not quite right;teedoes exactly what the option states and only ignoresSIGINT. All other signals are delivered as without-i.
– Andreas Wiese
Apr 4 '14 at 16:17
add a comment |
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.
answered Apr 4 '14 at 16:16
Andreas Wiese
1,771711
And in which situation this is important?
– hakre
Jul 4 '14 at 13:01
6
If you're usingteein a command line pipe likesome long running command | tee output, this might be helpful if you want to kill the input provider withCtrl+C, but wantteeto exit gracefully (by readingEOFfrom 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
add a comment |
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.
answered Apr 4 '14 at 16:16
Andreas Wiese
1,771711
And in which situation this is important?
– hakre
Jul 4 '14 at 13:01
6
If you're usingteein a command line pipe likesome long running command | tee output, this might be helpful if you want to kill the input provider withCtrl+C, but wantteeto exit gracefully (by readingEOFfrom 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
add a comment |
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.
answered Apr 4 '14 at 16:16
Andreas Wiese
1,771711
When called with -i, tee ignores the interrupt signal (SIGINT), which is normally issued by your terminal when hitting Ctrl+C.
answered Apr 4 '14 at 16:16
Andreas Wiese
1,771711
answered Apr 4 '14 at 16:16
Andreas Wiese
1,771711
answered Apr 4 '14 at 16:16
Andreas Wiese
1,771711
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 usingteein a command line pipe likesome long running command | tee output, this might be helpful if you want to kill the input provider withCtrl+C, but wantteeto exit gracefully (by readingEOFfrom 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
add a comment |
And in which situation this is important?
– hakre
Jul 4 '14 at 13:01
6
If you're usingteein a command line pipe likesome long running command | tee output, this might be helpful if you want to kill the input provider withCtrl+C, but wantteeto exit gracefully (by readingEOFfrom 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
add a comment |
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.
answered Apr 4 '14 at 14:50
Vasanta Koli
1011
1
That's not quite right;teedoes exactly what the option states and only ignoresSIGINT. All other signals are delivered as without-i.
– Andreas Wiese
Apr 4 '14 at 16:17
add a comment |
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.
answered Apr 4 '14 at 14:50
Vasanta Koli
1011
1
That's not quite right;teedoes exactly what the option states and only ignoresSIGINT. All other signals are delivered as without-i.
– Andreas Wiese
Apr 4 '14 at 16:17
add a comment |
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.
answered Apr 4 '14 at 14:50
Vasanta Koli
1011
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.
answered Apr 4 '14 at 14:50
Vasanta Koli
1011
answered Apr 4 '14 at 14:50
Vasanta Koli
1011
answered Apr 4 '14 at 14:50
Vasanta Koli
1011
answered Apr 4 '14 at 14:50
Vasanta Koli
1011
1011
1
That's not quite right;teedoes exactly what the option states and only ignoresSIGINT. All other signals are delivered as without-i.
– Andreas Wiese
Apr 4 '14 at 16:17
add a comment |
1
That's not quite right;teedoes exactly what the option states and only ignoresSIGINT. 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
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
