bug#33127: about run nohup command in Cygwin by ssh

[Bernhard Voelker]

tags 33127 notabug
close 33127
stop

On 10/23/18 9:40 AM, FORGET wrote:
> hello,
>     thanks for your time reading my mail.
>     when I use 'nohup' command in Cygwin, there is a problem.
>     steps as following:
>       1) ssh to a PC(windows installed Cygwin) by putty, we can call 
> puttyTerminal1
>       2) run command 'nohup /cygdrive/d/test/setup-x86_64.exe &'
>       3) use another ssh with same account to login to same pc (also by putty 
> window) , we can call puttyTerminal2
>       4) run command 'ps -ef|grep setup-x86'on puttyTerminal2, can see there 
> is a backend process running this exe.
>       5) close puttyTerminal1
>       6) run command 'ps -ef|grep setup-x86'on puttyTerminal2. the backend 
> process is gone.
>     
>       But when we use 'nohup', it should act always running backend, not gone 
> with disconnection of ssh, right?
>       I use putty, MobaXterm, results are all the same. So I think is not the 
> problem with clients of ssh. 
>       I use putty to connect with a Linux pc, when I close putty, backend 
> process with 'nohup' is still there.
>       Maybe there is something wrong with 'nohup' in Cygwin? 
>      
>     Here is my package info of cygwin. Hope it helps. 
>       Cygwin Package Information
>       Package                                    Version                    
> Status
>       _autorebase                                001007-1                   OK
>       openssh                                    7.8p1-1                    OK
>       openssl                                    1.0.2p-1                   OK
>     
>      thanks~~

Thanks for the report, but I'm afraid we cannot help you much here:
You reached the upstream GNU coreutils mailing list, but Cygwin seems
so special in that that I'd expect that nohup there is heavily patched
to work at all (... and probably also openssh).
Therefore, I'd like to redirect you to a Cygwin mailing list where you
might get better advice.

Thus, I'm marking this as "not a bug" in our bug tracker and closing
this as such.  Still, the discussion may continue, and we might also
reopen this issue if needed.

Have a nice day,
Berny