Mailing List Archive

[Bug 1988] ControlPersist causes stderr to be left open until the master connection times out
https://bugzilla.mindrot.org/show_bug.cgi?id=1988

--- Comment #3 from Damien Miller <djm@mindrot.org> 2012-03-30 11:39:32 EST ---
not necessarily - e.g. messages sent at loglevel fatal() or error()

--
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- 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
[Bug 1988] ControlPersist causes stderr to be left open until the master connection times out [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=1988

--- Comment #4 from Andrew McNabb <amcnabb@mcnabbs.org> 2012-04-01 03:35:25 EST ---
If ssh has forked a background daemon, the user can't reasonably expect
to see messages on stderr anyway. For example, they might close the
terminal in which the original ssh connection was created. Furthermore,
such messages might not even be welcome. After all, the user is
probably running some other application.

Any fatal errors would be relevant to other foreground ssh processes,
but not to a terminal window that is no longer running any ssh
processes.

Might the best long-term solution be to send any logging messages to
foreground ssh processes? In any case, I think it's incorrect to send
logging messages to a now-unrelated tty. Especially since this can make
scripts hang.

--
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- 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