Hello list, I observed a problem with interactive bash script executed by ssh: when I pressed <Ctrl+C>, ssh was killed on client side, but script remained active in remote machine and didn't receive signal INT. Using option -t gives no problem like that, but should it be perceived as a normal behaviour in case without -t? Please send a reply to my address too...
K?rlis Repsons wrote:> Please send a reply to my address too... > ... > I observed a problem with interactive bash script executed by ssh: when I > pressed <Ctrl+C>, ssh was killed on client side, but script remained active > in remote machine and didn't receive signal INT. > Using option -t gives no problem like that, but should it be perceived as a > normal behaviour in case without -t?The rsh command appeared in 4.2BSD. SSH is a secure replacement for it. The rsh man page includes the following in the bugs section: Stop signals stop the local rsh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain here. And therefore we know that this behavior has always been present. Although this functionality would be nice to have the implementation isn't completey straight-forward. There is an open bug tracking this behavior request and a patch in the tracker exists about it. https://bugzilla.mindrot.org/show_bug.cgi?id=396 Bob