https://bugzilla.mindrot.org/show_bug.cgi?id=3220
--- Comment #3 from Mikko Rantalainen <[email protected]> --- > I'm not seeing a problem here. [About issue (2):] All the other messages related to mux handling are debug1: debug1: setting up multiplex master socket debug1: control_persist_detach: backgrounding master process debug1: forking to background Why does this one specific message should be silenced only with Loglevel=quiet? I'd expect stderr (literally "standard error stream") to stay quiet by *default* unless there is at least one error. If I use verbose log level, then sure, emit these messages. > The message is sent to stderr, IMO accurate [...] [About issue (1):] Did you understand that that the shared connection *is not closed* despite the fact that the message says so? The process emitting that message is detaching from the shared connection but the shared connection is active and will not be closed because of process "B" in the example still using it. My point is that (1) the message is incorrect and (2) the message is not worth emitting unless verbose log is requested. With the current log level, even if you disable all warnings, errors and fatal errors(!), this message is still emitted. If you disagree with either (1) or (2), could you elaborate your reasoning? -- 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 [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
