How to keep screen running after exiting the command that runs in it?
I have the task to start a detached screen session (e.g. when the system reboots) and then to be able to connect to it and interrupt/kill the running process without the screen to terminate. Unfortunately when I attach to the screen session and stop the running command, the entire screen session terminates with:
[screen is terminating]
I am using the following command to start the detached screen:
screen -dm -S screen_name /bin/bash -c 'cd ~/mydir; npm start'
then I attach to the screen session using:
screen -r session_name
and if I Ctrl-C the npm, the bash command will exit and the screen is terminating.
What I want is to achieve a similar behaviour when attaching to the screen as if I would have started the npm inside the screen session manually:
screen -S session_name
and then inside the screen session:
cd ~/mydir
npm start
then I can Ctrl-C the npm command without the screen session being terminated.
bash gnu-screen
asked 11 hours ago
Gabriel Petrovay
1064
New contributor
Gabriel Petrovay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have the task to start a detached screen session (e.g. when the system reboots) and then to be able to connect to it and interrupt/kill the running process without the screen to terminate. Unfortunately when I attach to the screen session and stop the running command, the entire screen session terminates with:
[screen is terminating]
I am using the following command to start the detached screen:
screen -dm -S screen_name /bin/bash -c 'cd ~/mydir; npm start'
then I attach to the screen session using:
screen -r session_name
and if I Ctrl-C the npm, the bash command will exit and the screen is terminating.
What I want is to achieve a similar behaviour when attaching to the screen as if I would have started the npm inside the screen session manually:
screen -S session_name
and then inside the screen session:
cd ~/mydir
npm start
then I can Ctrl-C the npm command without the screen session being terminated.
bash gnu-screen
asked 11 hours ago
Gabriel Petrovay
1064
New contributor
Gabriel Petrovay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Not a good solution, but I cheat and start a second window so if I exit the first then screen doesn't terminate; egscreen -S myscreen -e ^Bb -m -d bash ; screen -S myscreen -x -X screen -t mytitle bash -c '/usr/local/bin/mycmd'
– Stephen Harris
9 hours ago
Or start the screen session differently, likebash -c 'cd ~/mydir; npm start; bash
– Jeff Schaller
14 mins ago
Potentially useful: unix.stackexchange.com/q/436959/117549
– Jeff Schaller
14 mins ago
add a comment |
I have the task to start a detached screen session (e.g. when the system reboots) and then to be able to connect to it and interrupt/kill the running process without the screen to terminate. Unfortunately when I attach to the screen session and stop the running command, the entire screen session terminates with:
[screen is terminating]
I am using the following command to start the detached screen:
screen -dm -S screen_name /bin/bash -c 'cd ~/mydir; npm start'
then I attach to the screen session using:
screen -r session_name
and if I Ctrl-C the npm, the bash command will exit and the screen is terminating.
What I want is to achieve a similar behaviour when attaching to the screen as if I would have started the npm inside the screen session manually:
screen -S session_name
and then inside the screen session:
cd ~/mydir
npm start
then I can Ctrl-C the npm command without the screen session being terminated.
bash gnu-screen
asked 11 hours ago
Gabriel Petrovay
1064
New contributor
Gabriel Petrovay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have the task to start a detached screen session (e.g. when the system reboots) and then to be able to connect to it and interrupt/kill the running process without the screen to terminate. Unfortunately when I attach to the screen session and stop the running command, the entire screen session terminates with:
[screen is terminating]
I am using the following command to start the detached screen:
screen -dm -S screen_name /bin/bash -c 'cd ~/mydir; npm start'
then I attach to the screen session using:
screen -r session_name
and if I Ctrl-C the npm, the bash command will exit and the screen is terminating.
What I want is to achieve a similar behaviour when attaching to the screen as if I would have started the npm inside the screen session manually:
screen -S session_name
and then inside the screen session:
cd ~/mydir
npm start
then I can Ctrl-C the npm command without the screen session being terminated.
bash gnu-screen
bash gnu-screen
asked 11 hours ago
Gabriel Petrovay
1064
New contributor
Gabriel Petrovay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 11 hours ago
Gabriel Petrovay
1064
New contributor
Gabriel Petrovay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 11 hours ago
Gabriel Petrovay
1064
New contributor
Gabriel Petrovay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 11 hours ago
Gabriel Petrovay
1064
asked 11 hours ago
Gabriel Petrovay
1064
1064
New contributor
Gabriel Petrovay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Gabriel Petrovay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Gabriel Petrovay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Not a good solution, but I cheat and start a second window so if I exit the first then screen doesn't terminate; egscreen -S myscreen -e ^Bb -m -d bash ; screen -S myscreen -x -X screen -t mytitle bash -c '/usr/local/bin/mycmd'
– Stephen Harris
9 hours ago
Or start the screen session differently, likebash -c 'cd ~/mydir; npm start; bash
– Jeff Schaller
14 mins ago
Potentially useful: unix.stackexchange.com/q/436959/117549
– Jeff Schaller
14 mins ago
add a comment |
Not a good solution, but I cheat and start a second window so if I exit the first then screen doesn't terminate; egscreen -S myscreen -e ^Bb -m -d bash ; screen -S myscreen -x -X screen -t mytitle bash -c '/usr/local/bin/mycmd'
– Stephen Harris
9 hours ago
Or start the screen session differently, likebash -c 'cd ~/mydir; npm start; bash
– Jeff Schaller
14 mins ago
Potentially useful: unix.stackexchange.com/q/436959/117549
– Jeff Schaller
14 mins ago
Not a good solution, but I cheat and start a second window so if I exit the first then screen doesn't terminate; eg
screen -S myscreen -e ^Bb -m -d bash ; screen -S myscreen -x -X screen -t mytitle bash -c '/usr/local/bin/mycmd'– Stephen Harris
9 hours ago
Not a good solution, but I cheat and start a second window so if I exit the first then screen doesn't terminate; eg
screen -S myscreen -e ^Bb -m -d bash ; screen -S myscreen -x -X screen -t mytitle bash -c '/usr/local/bin/mycmd'– Stephen Harris
9 hours ago
Or start the screen session differently, like
bash -c 'cd ~/mydir; npm start; bash– Jeff Schaller
14 mins ago
Or start the screen session differently, like
bash -c 'cd ~/mydir; npm start; bash– Jeff Schaller
14 mins ago
Potentially useful: unix.stackexchange.com/q/436959/117549
– Jeff Schaller
14 mins ago
Potentially useful: unix.stackexchange.com/q/436959/117549
– Jeff Schaller
14 mins ago
add a comment |
active
oldest
votes
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
});
}
});
Gabriel Petrovay is a new contributor. Be nice, and check out our Code of Conduct.
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%2f490508%2fhow-to-keep-screen-running-after-exiting-the-command-that-runs-in-it%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Gabriel Petrovay is a new contributor. Be nice, and check out our Code of Conduct.
Gabriel Petrovay is a new contributor. Be nice, and check out our Code of Conduct.
Gabriel Petrovay is a new contributor. Be nice, and check out our Code of Conduct.
Gabriel Petrovay is a new contributor. Be nice, and check out our Code of Conduct.
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.
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%2f490508%2fhow-to-keep-screen-running-after-exiting-the-command-that-runs-in-it%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
Not a good solution, but I cheat and start a second window so if I exit the first then screen doesn't terminate; eg
screen -S myscreen -e ^Bb -m -d bash ; screen -S myscreen -x -X screen -t mytitle bash -c '/usr/local/bin/mycmd'– Stephen Harris
9 hours ago
Or start the screen session differently, like
bash -c 'cd ~/mydir; npm start; bash– Jeff Schaller
14 mins ago
Potentially useful: unix.stackexchange.com/q/436959/117549
– Jeff Schaller
14 mins ago