Page 1 of 1

A nohup bug?

PostPosted: Jun 16th, '16, 19:09
by mla
Maybe my Unix/Linux is too rusty, but the nohup command seems to be bugged.

I have an ssh session to a remote machine with the DISPLAY variable set to my current screen. I start an X application (e.g. firefox) with "nohup firefox &". If I now exit the remote shell (be it with ^D or exit), the response is "logout"... and nothing happens. That ssh session just sits there, echoing what I type but not doing anything. If I hit ^C, the ssh session terminates but so does the process started with nohup! Surely, that's not supposed to happen!

Re: A nohup bug?

PostPosted: Jun 17th, '16, 17:51
by doktor5000
So you want your firefox to still be running when you logoff, right?

Can you try if it works differently if you use disown instead of nohup, at least when using bash?
Code: Select all
firefox disown &

should work the same way.

Re: A nohup bug?

PostPosted: Jun 17th, '16, 18:33
by mla
Same problem with disown. Yes, given my firefox problems, I wanted to start a completely detached firefox on the remote machine. Surely that must be possible. (I am sure I remember using nohup under bash on Unix to do this some years ago.)