openssh bugs - Mar 2010 - [Bug 1118] Annoying "Killed by signal 1" message with ProxyCommand

https://bugzilla.mindrot.org/show_bug.cgi?id=1118

--- Comment #4 from Colin Watson <cjwatson at debian.org> 2010-03-02
02:50:08 EST ---
Created an attachment (id=1803)
 --> (https://bugzilla.mindrot.org/attachment.cgi?id=1803)
debug() and cleanup_exit() on signal rather than fatal()

-- 
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=1118

--- Comment #5 from Colin Watson <cjwatson at debian.org> 2010-03-02
02:51:34 EST ---
Closely related to this, it was pointed out to me in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=313371#10 that ssh
really shouldn't print a message when it's killed by SIGTERM or SIGINT,
since those typically correspond to explicit user actions which the
user doesn't need to be told about again.  Does this make sense to you
as well?

For the sake of completeness, I've attached the patch that we're
currently using in Debian to reduce these errors to debug messages.  At
the time I didn't realise that -q would suppress output from fatal(),
though, so I may drop this patch once I've looked into whether any
dependent software in Debian still needs it.

It is perhaps worth noting that this patch also produces a more
accurate exit code ...

-- 
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.