How do I implement/enable blanket nohup in the shell?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












Something like a shell option or "mode" that protects all GUI processes run within that session from being killed when I kill the shell. It would be the equivalent of using nohup for each of the processes.




bash nohup




share|improve this question




















  • To make this extra clear. I want to be able to kill the shell (including its virtual terminal, or tmux, or screen) without this killing its processes. So no, by shell I did not just mean virtual terminal.
    – argle
    Feb 7 at 21:51










  • Shell has no way of knowing whether or not if process is GUI program or not, so I doubt there's a way to "automate" that. Personally, if I know it's a GUI app, I run it with nohup gui_app > /dev/null 2>&1 & right away.
    – Sergiy Kolodyazhnyy
    Feb 7 at 22:54










  • Yes, but the shell has no way of knowing whether the process is GUI or not either.
    – argle
    Feb 7 at 23:03










  • And your point is ?
    – Sergiy Kolodyazhnyy
    Feb 7 at 23:28










  • My nohup mode doesn't care if things break with some applications. It was an argument against "shifting the... question".
    – argle
    Feb 8 at 8:37














up vote
0
down vote

favorite












Something like a shell option or "mode" that protects all GUI processes run within that session from being killed when I kill the shell. It would be the equivalent of using nohup for each of the processes.




bash nohup




share|improve this question




















  • To make this extra clear. I want to be able to kill the shell (including its virtual terminal, or tmux, or screen) without this killing its processes. So no, by shell I did not just mean virtual terminal.
    – argle
    Feb 7 at 21:51










  • Shell has no way of knowing whether or not if process is GUI program or not, so I doubt there's a way to "automate" that. Personally, if I know it's a GUI app, I run it with nohup gui_app > /dev/null 2>&1 & right away.
    – Sergiy Kolodyazhnyy
    Feb 7 at 22:54










  • Yes, but the shell has no way of knowing whether the process is GUI or not either.
    – argle
    Feb 7 at 23:03










  • And your point is ?
    – Sergiy Kolodyazhnyy
    Feb 7 at 23:28










  • My nohup mode doesn't care if things break with some applications. It was an argument against "shifting the... question".
    – argle
    Feb 8 at 8:37












up vote
0
down vote

favorite









up vote
0
down vote

favorite











Something like a shell option or "mode" that protects all GUI processes run within that session from being killed when I kill the shell. It would be the equivalent of using nohup for each of the processes.




bash nohup




share|improve this question












Something like a shell option or "mode" that protects all GUI processes run within that session from being killed when I kill the shell. It would be the equivalent of using nohup for each of the processes.





bash nohup





share|improve this question











share|improve this question




share|improve this question










asked Feb 7 at 19:18









argle

331115




331115











  • To make this extra clear. I want to be able to kill the shell (including its virtual terminal, or tmux, or screen) without this killing its processes. So no, by shell I did not just mean virtual terminal.
    – argle
    Feb 7 at 21:51










  • Shell has no way of knowing whether or not if process is GUI program or not, so I doubt there's a way to "automate" that. Personally, if I know it's a GUI app, I run it with nohup gui_app > /dev/null 2>&1 & right away.
    – Sergiy Kolodyazhnyy
    Feb 7 at 22:54










  • Yes, but the shell has no way of knowing whether the process is GUI or not either.
    – argle
    Feb 7 at 23:03










  • And your point is ?
    – Sergiy Kolodyazhnyy
    Feb 7 at 23:28










  • My nohup mode doesn't care if things break with some applications. It was an argument against "shifting the... question".
    – argle
    Feb 8 at 8:37
















  • To make this extra clear. I want to be able to kill the shell (including its virtual terminal, or tmux, or screen) without this killing its processes. So no, by shell I did not just mean virtual terminal.
    – argle
    Feb 7 at 21:51










  • Shell has no way of knowing whether or not if process is GUI program or not, so I doubt there's a way to "automate" that. Personally, if I know it's a GUI app, I run it with nohup gui_app > /dev/null 2>&1 & right away.
    – Sergiy Kolodyazhnyy
    Feb 7 at 22:54










  • Yes, but the shell has no way of knowing whether the process is GUI or not either.
    – argle
    Feb 7 at 23:03










  • And your point is ?
    – Sergiy Kolodyazhnyy
    Feb 7 at 23:28










  • My nohup mode doesn't care if things break with some applications. It was an argument against "shifting the... question".
    – argle
    Feb 8 at 8:37















To make this extra clear. I want to be able to kill the shell (including its virtual terminal, or tmux, or screen) without this killing its processes. So no, by shell I did not just mean virtual terminal.
– argle
Feb 7 at 21:51




To make this extra clear. I want to be able to kill the shell (including its virtual terminal, or tmux, or screen) without this killing its processes. So no, by shell I did not just mean virtual terminal.
– argle
Feb 7 at 21:51












Shell has no way of knowing whether or not if process is GUI program or not, so I doubt there's a way to "automate" that. Personally, if I know it's a GUI app, I run it with nohup gui_app > /dev/null 2>&1 & right away.
– Sergiy Kolodyazhnyy
Feb 7 at 22:54




Shell has no way of knowing whether or not if process is GUI program or not, so I doubt there's a way to "automate" that. Personally, if I know it's a GUI app, I run it with nohup gui_app > /dev/null 2>&1 & right away.
– Sergiy Kolodyazhnyy
Feb 7 at 22:54












Yes, but the shell has no way of knowing whether the process is GUI or not either.
– argle
Feb 7 at 23:03




Yes, but the shell has no way of knowing whether the process is GUI or not either.
– argle
Feb 7 at 23:03












And your point is ?
– Sergiy Kolodyazhnyy
Feb 7 at 23:28




And your point is ?
– Sergiy Kolodyazhnyy
Feb 7 at 23:28












My nohup mode doesn't care if things break with some applications. It was an argument against "shifting the... question".
– argle
Feb 8 at 8:37




My nohup mode doesn't care if things break with some applications. It was an argument against "shifting the... question".
– argle
Feb 8 at 8:37










1 Answer
1






active

oldest

votes

















up vote
-1
down vote













One solution is to run all commands inside of a terminal multiplexer like tmux or GNU screen. Then if you detach from the tumx or screen session or are disconnected from an ssh session, the commands you are running will continue and not get a SIGHUP. You can reattach and essentially pick up where you left off.



This method is a great way to do any remote administration where you do not want to get disconnected while doing something important or long running.






share|improve this answer






















  • ... unless systemd gets frisky and for some reason nukes some processes
    – thrig
    Feb 7 at 19:22










  • also no protection against lasers either.
    – datUser
    Feb 7 at 19:25










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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f422633%2fhow-do-i-implement-enable-blanket-nohup-in-the-shell%23new-answer', 'question_page');

);

Post as a guest

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
-1
down vote













One solution is to run all commands inside of a terminal multiplexer like tmux or GNU screen. Then if you detach from the tumx or screen session or are disconnected from an ssh session, the commands you are running will continue and not get a SIGHUP. You can reattach and essentially pick up where you left off.



This method is a great way to do any remote administration where you do not want to get disconnected while doing something important or long running.






share|improve this answer






















  • ... unless systemd gets frisky and for some reason nukes some processes
    – thrig
    Feb 7 at 19:22










  • also no protection against lasers either.
    – datUser
    Feb 7 at 19:25














up vote
-1
down vote













One solution is to run all commands inside of a terminal multiplexer like tmux or GNU screen. Then if you detach from the tumx or screen session or are disconnected from an ssh session, the commands you are running will continue and not get a SIGHUP. You can reattach and essentially pick up where you left off.



This method is a great way to do any remote administration where you do not want to get disconnected while doing something important or long running.






share|improve this answer






















  • ... unless systemd gets frisky and for some reason nukes some processes
    – thrig
    Feb 7 at 19:22










  • also no protection against lasers either.
    – datUser
    Feb 7 at 19:25












up vote
-1
down vote










up vote
-1
down vote









One solution is to run all commands inside of a terminal multiplexer like tmux or GNU screen. Then if you detach from the tumx or screen session or are disconnected from an ssh session, the commands you are running will continue and not get a SIGHUP. You can reattach and essentially pick up where you left off.



This method is a great way to do any remote administration where you do not want to get disconnected while doing something important or long running.






share|improve this answer














One solution is to run all commands inside of a terminal multiplexer like tmux or GNU screen. Then if you detach from the tumx or screen session or are disconnected from an ssh session, the commands you are running will continue and not get a SIGHUP. You can reattach and essentially pick up where you left off.



This method is a great way to do any remote administration where you do not want to get disconnected while doing something important or long running.







share|improve this answer














share|improve this answer



share|improve this answer








edited Feb 7 at 19:24

























answered Feb 7 at 19:21









datUser

2,2811032




2,2811032











  • ... unless systemd gets frisky and for some reason nukes some processes
    – thrig
    Feb 7 at 19:22










  • also no protection against lasers either.
    – datUser
    Feb 7 at 19:25
















  • ... unless systemd gets frisky and for some reason nukes some processes
    – thrig
    Feb 7 at 19:22










  • also no protection against lasers either.
    – datUser
    Feb 7 at 19:25















... unless systemd gets frisky and for some reason nukes some processes
– thrig
Feb 7 at 19:22




... unless systemd gets frisky and for some reason nukes some processes
– thrig
Feb 7 at 19:22












also no protection against lasers either.
– datUser
Feb 7 at 19:25




also no protection against lasers either.
– datUser
Feb 7 at 19:25












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f422633%2fhow-do-i-implement-enable-blanket-nohup-in-the-shell%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Se
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fix it? –
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this
Read more