Signal trap from background job without pressing enter
Clash Royale CLAN TAG#URR8PPP
In Bash 5 I ran into a situation where I want to do the following:
trap 'echo trapped!' USR1
while true; do kill -SIGUSR1 $$; sleep 1; done &
But I have to press enter on keyboard every time the signal is sent to make the trap code continue.
Actually I expect the trap to be executed without any keyboard interaction.
EDIT:
Finally I got it working like this:
trap 'echo trapped!' USR1
while true; do kill -USR1 $$; kill -INT $$; sleep 1; done &
But I consider the solution as workaround and not as answer.
bash shell-script background-process signals trap
add a comment |
In Bash 5 I ran into a situation where I want to do the following:
trap 'echo trapped!' USR1
while true; do kill -SIGUSR1 $$; sleep 1; done &
But I have to press enter on keyboard every time the signal is sent to make the trap code continue.
Actually I expect the trap to be executed without any keyboard interaction.
EDIT:
Finally I got it working like this:
trap 'echo trapped!' USR1
while true; do kill -USR1 $$; kill -INT $$; sleep 1; done &
But I consider the solution as workaround and not as answer.
bash shell-script background-process signals trap
add a comment |
In Bash 5 I ran into a situation where I want to do the following:
trap 'echo trapped!' USR1
while true; do kill -SIGUSR1 $$; sleep 1; done &
But I have to press enter on keyboard every time the signal is sent to make the trap code continue.
Actually I expect the trap to be executed without any keyboard interaction.
EDIT:
Finally I got it working like this:
trap 'echo trapped!' USR1
while true; do kill -USR1 $$; kill -INT $$; sleep 1; done &
But I consider the solution as workaround and not as answer.
bash shell-script background-process signals trap
In Bash 5 I ran into a situation where I want to do the following:
trap 'echo trapped!' USR1
while true; do kill -SIGUSR1 $$; sleep 1; done &
But I have to press enter on keyboard every time the signal is sent to make the trap code continue.
Actually I expect the trap to be executed without any keyboard interaction.
EDIT:
Finally I got it working like this:
trap 'echo trapped!' USR1
while true; do kill -USR1 $$; kill -INT $$; sleep 1; done &
But I consider the solution as workaround and not as answer.
bash shell-script background-process signals trap
bash shell-script background-process signals trap
edited Feb 17 at 22:14
Dominik Kummer
asked Feb 17 at 20:47
Dominik KummerDominik Kummer
788
788
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Someone seems to have a very similar problem here.
Long story short if it's OK to execute the command from the trap built-in in a subprocess ('echo trapped!' in this case). You can put your commands in a file (for example a.sh
):
trap 'echo trapped!' USR1
while true; do kill -USR1 $$; sleep 1; done
and execute the file as a background process with bash a.sh &
If it's not okay to do it in a subprocess there is no good solution since the interactive shell does a blocking read operation while waiting for the user to enter a command and it doesn't handle most signals while that is happening (as you have noticed it does handle SIGINT). The solution above works since the trap is in a non-interactive shell (thus it is not in the middle of a blocking read when it gets the signal).
add a comment |
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
);
);
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%2funix.stackexchange.com%2fquestions%2f501235%2fsignal-trap-from-background-job-without-pressing-enter%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Someone seems to have a very similar problem here.
Long story short if it's OK to execute the command from the trap built-in in a subprocess ('echo trapped!' in this case). You can put your commands in a file (for example a.sh
):
trap 'echo trapped!' USR1
while true; do kill -USR1 $$; sleep 1; done
and execute the file as a background process with bash a.sh &
If it's not okay to do it in a subprocess there is no good solution since the interactive shell does a blocking read operation while waiting for the user to enter a command and it doesn't handle most signals while that is happening (as you have noticed it does handle SIGINT). The solution above works since the trap is in a non-interactive shell (thus it is not in the middle of a blocking read when it gets the signal).
add a comment |
Someone seems to have a very similar problem here.
Long story short if it's OK to execute the command from the trap built-in in a subprocess ('echo trapped!' in this case). You can put your commands in a file (for example a.sh
):
trap 'echo trapped!' USR1
while true; do kill -USR1 $$; sleep 1; done
and execute the file as a background process with bash a.sh &
If it's not okay to do it in a subprocess there is no good solution since the interactive shell does a blocking read operation while waiting for the user to enter a command and it doesn't handle most signals while that is happening (as you have noticed it does handle SIGINT). The solution above works since the trap is in a non-interactive shell (thus it is not in the middle of a blocking read when it gets the signal).
add a comment |
Someone seems to have a very similar problem here.
Long story short if it's OK to execute the command from the trap built-in in a subprocess ('echo trapped!' in this case). You can put your commands in a file (for example a.sh
):
trap 'echo trapped!' USR1
while true; do kill -USR1 $$; sleep 1; done
and execute the file as a background process with bash a.sh &
If it's not okay to do it in a subprocess there is no good solution since the interactive shell does a blocking read operation while waiting for the user to enter a command and it doesn't handle most signals while that is happening (as you have noticed it does handle SIGINT). The solution above works since the trap is in a non-interactive shell (thus it is not in the middle of a blocking read when it gets the signal).
Someone seems to have a very similar problem here.
Long story short if it's OK to execute the command from the trap built-in in a subprocess ('echo trapped!' in this case). You can put your commands in a file (for example a.sh
):
trap 'echo trapped!' USR1
while true; do kill -USR1 $$; sleep 1; done
and execute the file as a background process with bash a.sh &
If it's not okay to do it in a subprocess there is no good solution since the interactive shell does a blocking read operation while waiting for the user to enter a command and it doesn't handle most signals while that is happening (as you have noticed it does handle SIGINT). The solution above works since the trap is in a non-interactive shell (thus it is not in the middle of a blocking read when it gets the signal).
answered Feb 17 at 23:27
Daniel AtanasovDaniel Atanasov
544
544
add a comment |
add a comment |
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.
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%2funix.stackexchange.com%2fquestions%2f501235%2fsignal-trap-from-background-job-without-pressing-enter%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