https://bugzilla.mindrot.org/show_bug.cgi?id=3550
--- Comment #5 from maggiezhu...@163.com --- (In reply to Darren Tucker from comment #4) > (In reply to maggiezhuooo from comment #3) > > Now this ^C will make ssh exit under ssh -t command. > > That's probably not what's happening. What's probably happening is > that the ssh is forwarding the SIGINT to the server which is > delivering it to the remote program, which then exits. When it > exits, the ssh reads its exit status then exits itself. You can see > this if you turn on ssh debugging: > > $ ssh -v -t localhost sleep 60 > [...] > debug1: Sending command: sleep 60 > ^C > debug1: client_input_channel_req: channel 0 rtype exit-signal reply 0 > debug1: client_input_channel_req: channel 0 rtype e...@openssh.com > reply 0 > debug1: channel 0: free: client-session, nchannels 1 > Connection to localhost closed. > > > Could you elaborate on what you're trying to do? Thanks for your reply! Sorry to bother you again, but when I run an app on a remote server using ssh -t command, when I type ^c, the app stops running and SSH shuts down with it. I want SSH to not shut down with the app stopping, i.e. when the app returns to a stopped state, is there a way to make SSH ignore this state and continue running? Because I want to continue to use ssh to interact with the remote server. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
