Disable screen outputting “[screen is terminating]” Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election Results Why I closed the “Why is Kali so hard” questionWhy doesn't Alpine's viewer command work within GNU screen and how can I fix it?How to write a shell script to run multiple command in different screen sessions?Problem connecting with Beagleboard through serial?How to prevent GNU screen from clearing the screen when terminating?ssh -> screen -> ssh - how to kill remote screened ssh without killing original ssh sessionHow can I save the output of a detached screen with script?Programmatically run background tasks in a split screen?How to fix gnu screen term detection when started on detached mode?Get a list of children process ids (PIDs) running in a screen sessionScreen session doesn't close after script has run
Is the Standard Deduction better than Itemized when both are the same amount?
Extract all GPU name, model and GPU ram
How can I make names more distinctive without making them longer?
Can I cast Passwall to drop an enemy into a 20-foot pit?
Why are there no cargo aircraft with "flying wing" design?
Can an alien society believe that their star system is the universe?
What's the purpose of writing one's academic biography in the third person?
How to tell that you are a giant?
Storing hydrofluoric acid before the invention of plastics
English words in a non-english sci-fi novel
Apollo command module space walk?
porting install scripts : can rpm replace apt?
What is the role of the transistor and diode in a soft start circuit?
How to answer "Have you ever been terminated?"
Why light coming from distant stars is not discreet?
Why did the Falcon Heavy center core fall off the ASDS OCISLY barge?
Identify plant with long narrow paired leaves and reddish stems
Can a USB port passively 'listen only'?
Bete Noir -- no dairy
What is Arya's weapon design?
Why do we bend a book to keep it straight?
Can a non-EU citizen traveling with me come with me through the EU passport line?
How to find all the available tools in mac terminal?
Do I really need recursive chmod to restrict access to a folder?
Disable screen outputting “[screen is terminating]”
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionWhy doesn't Alpine's viewer command work within GNU screen and how can I fix it?How to write a shell script to run multiple command in different screen sessions?Problem connecting with Beagleboard through serial?How to prevent GNU screen from clearing the screen when terminating?ssh -> screen -> ssh - how to kill remote screened ssh without killing original ssh sessionHow can I save the output of a detached screen with script?Programmatically run background tasks in a split screen?How to fix gnu screen term detection when started on detached mode?Get a list of children process ids (PIDs) running in a screen sessionScreen session doesn't close after script has run
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
How do I disable the output when you are done with a screen from the screen
command?
Example:
function foo()
echo "Testing..."
sleep 2
echo "Done!"
export -f foo
screen -q bash -c "foo" &> /dev/null
It all works as expected, however I cannot find out how to disable the "[screen is terminating]".
gnu-screen
add a comment |
How do I disable the output when you are done with a screen from the screen
command?
Example:
function foo()
echo "Testing..."
sleep 2
echo "Done!"
export -f foo
screen -q bash -c "foo" &> /dev/null
It all works as expected, however I cannot find out how to disable the "[screen is terminating]".
gnu-screen
3
Screen runs detached from your terminal, so you can't use the pipe like you would expect, this won't work for example:screen -q bash -c "foo" | head -n -1 &> /dev/null
. So the real question is why do you care about this one line of text? If you can answer that, then maybe we can find a solution to that problem.
– totaam
Dec 31 '11 at 19:28
add a comment |
How do I disable the output when you are done with a screen from the screen
command?
Example:
function foo()
echo "Testing..."
sleep 2
echo "Done!"
export -f foo
screen -q bash -c "foo" &> /dev/null
It all works as expected, however I cannot find out how to disable the "[screen is terminating]".
gnu-screen
How do I disable the output when you are done with a screen from the screen
command?
Example:
function foo()
echo "Testing..."
sleep 2
echo "Done!"
export -f foo
screen -q bash -c "foo" &> /dev/null
It all works as expected, however I cannot find out how to disable the "[screen is terminating]".
gnu-screen
gnu-screen
edited Dec 31 '11 at 21:45
Gilles
548k13011131631
548k13011131631
asked Dec 31 '11 at 3:21
TyiloTyilo
2,16773254
2,16773254
3
Screen runs detached from your terminal, so you can't use the pipe like you would expect, this won't work for example:screen -q bash -c "foo" | head -n -1 &> /dev/null
. So the real question is why do you care about this one line of text? If you can answer that, then maybe we can find a solution to that problem.
– totaam
Dec 31 '11 at 19:28
add a comment |
3
Screen runs detached from your terminal, so you can't use the pipe like you would expect, this won't work for example:screen -q bash -c "foo" | head -n -1 &> /dev/null
. So the real question is why do you care about this one line of text? If you can answer that, then maybe we can find a solution to that problem.
– totaam
Dec 31 '11 at 19:28
3
3
Screen runs detached from your terminal, so you can't use the pipe like you would expect, this won't work for example:
screen -q bash -c "foo" | head -n -1 &> /dev/null
. So the real question is why do you care about this one line of text? If you can answer that, then maybe we can find a solution to that problem.– totaam
Dec 31 '11 at 19:28
Screen runs detached from your terminal, so you can't use the pipe like you would expect, this won't work for example:
screen -q bash -c "foo" | head -n -1 &> /dev/null
. So the real question is why do you care about this one line of text? If you can answer that, then maybe we can find a solution to that problem.– totaam
Dec 31 '11 at 19:28
add a comment |
3 Answers
3
active
oldest
votes
There are only two solutions that I can think of. The first is to modify the screen code itself and recompile. The second is to have something like an expect
wrapper around the program (untested):
#!/usr/bin/expect -f
spawn screen -q bash -c foo
interact
"[screen is terminating]" exit
add a comment |
The screen is using your tty to write that text, so you can't stop the screen to write that text by just redirect stdout or stderr to the /dev/null
.
I have the simplest way for removing that line from an output.
In this approach you need to move the cursor upward and clear that line.
Escape characters can help you with that, for example,to execute the screen
command with cat
command, you need to execute that like:
screen cat;echo -en 'e[Ae[K'
This will remove the line [screen is terminating]
.
2
Better asprintf '33[A33[K'
is manyecho
implementations don't support-n
or-e
(Unix compliant ones would needecho '33[A33[Kc'
). Or usetput cuu1; tput el
to avoid hardcoding the sequences of a specific terminal.
– Stéphane Chazelas
May 5 '17 at 11:50
add a comment |
Simple :D
The only way is to modify the "screen" executable.
The best (portable) way to do so is something like this:
offset=$(tr -c '[[:print:]]' 'n' <`which screen`|grep -b "screen is terminating" | cut -d ":" -f 1)
printf "x00" | dd of=`which screen` obs=1 seek=$offset conv=notrunc
obviously the script must be re-run every time the package is updated.
1
sorry I was in a rush...I'll update it now.
– Zibri
Dec 20 '18 at 19:54
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%2f28043%2fdisable-screen-outputting-screen-is-terminating%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are only two solutions that I can think of. The first is to modify the screen code itself and recompile. The second is to have something like an expect
wrapper around the program (untested):
#!/usr/bin/expect -f
spawn screen -q bash -c foo
interact
"[screen is terminating]" exit
add a comment |
There are only two solutions that I can think of. The first is to modify the screen code itself and recompile. The second is to have something like an expect
wrapper around the program (untested):
#!/usr/bin/expect -f
spawn screen -q bash -c foo
interact
"[screen is terminating]" exit
add a comment |
There are only two solutions that I can think of. The first is to modify the screen code itself and recompile. The second is to have something like an expect
wrapper around the program (untested):
#!/usr/bin/expect -f
spawn screen -q bash -c foo
interact
"[screen is terminating]" exit
There are only two solutions that I can think of. The first is to modify the screen code itself and recompile. The second is to have something like an expect
wrapper around the program (untested):
#!/usr/bin/expect -f
spawn screen -q bash -c foo
interact
"[screen is terminating]" exit
answered Dec 31 '11 at 22:48
ArcegeArcege
17.4k44257
17.4k44257
add a comment |
add a comment |
The screen is using your tty to write that text, so you can't stop the screen to write that text by just redirect stdout or stderr to the /dev/null
.
I have the simplest way for removing that line from an output.
In this approach you need to move the cursor upward and clear that line.
Escape characters can help you with that, for example,to execute the screen
command with cat
command, you need to execute that like:
screen cat;echo -en 'e[Ae[K'
This will remove the line [screen is terminating]
.
2
Better asprintf '33[A33[K'
is manyecho
implementations don't support-n
or-e
(Unix compliant ones would needecho '33[A33[Kc'
). Or usetput cuu1; tput el
to avoid hardcoding the sequences of a specific terminal.
– Stéphane Chazelas
May 5 '17 at 11:50
add a comment |
The screen is using your tty to write that text, so you can't stop the screen to write that text by just redirect stdout or stderr to the /dev/null
.
I have the simplest way for removing that line from an output.
In this approach you need to move the cursor upward and clear that line.
Escape characters can help you with that, for example,to execute the screen
command with cat
command, you need to execute that like:
screen cat;echo -en 'e[Ae[K'
This will remove the line [screen is terminating]
.
2
Better asprintf '33[A33[K'
is manyecho
implementations don't support-n
or-e
(Unix compliant ones would needecho '33[A33[Kc'
). Or usetput cuu1; tput el
to avoid hardcoding the sequences of a specific terminal.
– Stéphane Chazelas
May 5 '17 at 11:50
add a comment |
The screen is using your tty to write that text, so you can't stop the screen to write that text by just redirect stdout or stderr to the /dev/null
.
I have the simplest way for removing that line from an output.
In this approach you need to move the cursor upward and clear that line.
Escape characters can help you with that, for example,to execute the screen
command with cat
command, you need to execute that like:
screen cat;echo -en 'e[Ae[K'
This will remove the line [screen is terminating]
.
The screen is using your tty to write that text, so you can't stop the screen to write that text by just redirect stdout or stderr to the /dev/null
.
I have the simplest way for removing that line from an output.
In this approach you need to move the cursor upward and clear that line.
Escape characters can help you with that, for example,to execute the screen
command with cat
command, you need to execute that like:
screen cat;echo -en 'e[Ae[K'
This will remove the line [screen is terminating]
.
edited 11 hours ago
Rui F Ribeiro
42.1k1484142
42.1k1484142
answered May 5 '17 at 11:41
purushothaman poovaipurushothaman poovai
113
113
2
Better asprintf '33[A33[K'
is manyecho
implementations don't support-n
or-e
(Unix compliant ones would needecho '33[A33[Kc'
). Or usetput cuu1; tput el
to avoid hardcoding the sequences of a specific terminal.
– Stéphane Chazelas
May 5 '17 at 11:50
add a comment |
2
Better asprintf '33[A33[K'
is manyecho
implementations don't support-n
or-e
(Unix compliant ones would needecho '33[A33[Kc'
). Or usetput cuu1; tput el
to avoid hardcoding the sequences of a specific terminal.
– Stéphane Chazelas
May 5 '17 at 11:50
2
2
Better as
printf '33[A33[K'
is many echo
implementations don't support -n
or -e
(Unix compliant ones would need echo '33[A33[Kc'
). Or use tput cuu1; tput el
to avoid hardcoding the sequences of a specific terminal.– Stéphane Chazelas
May 5 '17 at 11:50
Better as
printf '33[A33[K'
is many echo
implementations don't support -n
or -e
(Unix compliant ones would need echo '33[A33[Kc'
). Or use tput cuu1; tput el
to avoid hardcoding the sequences of a specific terminal.– Stéphane Chazelas
May 5 '17 at 11:50
add a comment |
Simple :D
The only way is to modify the "screen" executable.
The best (portable) way to do so is something like this:
offset=$(tr -c '[[:print:]]' 'n' <`which screen`|grep -b "screen is terminating" | cut -d ":" -f 1)
printf "x00" | dd of=`which screen` obs=1 seek=$offset conv=notrunc
obviously the script must be re-run every time the package is updated.
1
sorry I was in a rush...I'll update it now.
– Zibri
Dec 20 '18 at 19:54
add a comment |
Simple :D
The only way is to modify the "screen" executable.
The best (portable) way to do so is something like this:
offset=$(tr -c '[[:print:]]' 'n' <`which screen`|grep -b "screen is terminating" | cut -d ":" -f 1)
printf "x00" | dd of=`which screen` obs=1 seek=$offset conv=notrunc
obviously the script must be re-run every time the package is updated.
1
sorry I was in a rush...I'll update it now.
– Zibri
Dec 20 '18 at 19:54
add a comment |
Simple :D
The only way is to modify the "screen" executable.
The best (portable) way to do so is something like this:
offset=$(tr -c '[[:print:]]' 'n' <`which screen`|grep -b "screen is terminating" | cut -d ":" -f 1)
printf "x00" | dd of=`which screen` obs=1 seek=$offset conv=notrunc
obviously the script must be re-run every time the package is updated.
Simple :D
The only way is to modify the "screen" executable.
The best (portable) way to do so is something like this:
offset=$(tr -c '[[:print:]]' 'n' <`which screen`|grep -b "screen is terminating" | cut -d ":" -f 1)
printf "x00" | dd of=`which screen` obs=1 seek=$offset conv=notrunc
obviously the script must be re-run every time the package is updated.
edited 11 hours ago
Rui F Ribeiro
42.1k1484142
42.1k1484142
answered Dec 12 '18 at 13:18
ZibriZibri
16926
16926
1
sorry I was in a rush...I'll update it now.
– Zibri
Dec 20 '18 at 19:54
add a comment |
1
sorry I was in a rush...I'll update it now.
– Zibri
Dec 20 '18 at 19:54
1
1
sorry I was in a rush...I'll update it now.
– Zibri
Dec 20 '18 at 19:54
sorry I was in a rush...I'll update it now.
– Zibri
Dec 20 '18 at 19:54
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%2f28043%2fdisable-screen-outputting-screen-is-terminating%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
-gnu-screen
3
Screen runs detached from your terminal, so you can't use the pipe like you would expect, this won't work for example:
screen -q bash -c "foo" | head -n -1 &> /dev/null
. So the real question is why do you care about this one line of text? If you can answer that, then maybe we can find a solution to that problem.– totaam
Dec 31 '11 at 19:28