[ale] After 15 years, Nohup is sttll broken???

[Chris Fowler]

> From: "Lightner, Jeffrey" <JLightner at dsservices.com>
> To: "Chris Fowler" <cfowler at outpostsentinel.com>, "Atlanta Linux Enthusiasts"
> <ale at ale.org>, neal at mnopltd.com
> Sent: Wednesday, July 31, 2019 11:01:40 AM
> Subject: RE: After 15 years, Nohup is sttll broken???

> I gather you're doing an ssh from one system to another. I wonder if your shell
> default on either the system you're coming from or the second system has TMOUT
> variable set and it is thinking the session is idle due to lack of output. If
> so, doing an unset TMOUT might solve it. Note I have seen issues where firewall
> devices will timeout sessions such as VPN but I can full them by running a
> while loop in another window to just display data to the screen every 5
> minutes.

> As posted by someone else I typically run:
> nohup <script> &

One simple thing that may work in his case: 

( nohup <script> & disown) 

I use '()' to spawn sub-shell 

disown with no arguments will affect all current jobs. It is easier to simply use () than to do a job list and pick out the job. The command is also a bash built-in. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.ale.org/pipermail/ale/attachments/20190731/91912451/attachment.html>