Re: [libvirt] [PATCH] char: drop data written to a disconnected pty
On Tue, Jan 31, 2017 at 6:06 AM, Marc-André Lureau <mlureau(a)redhat.com> wrote:
I think this can be confusing if some backends silently drop the data
(under disconnected state), while other don't. Perhaps we should have instead a new
common chardev property "hup-drop" ? (suggestions for better name welcome)
Either way, when a pty is disconnected data will get dropped, whether
by the pty backend (as proposed) or by the serial port device or other
frontend (as currently).
The only difference from a user's perspective is whether the dropped
data gets written to the log file, which is the main motivation for
this change. The backward compatibility concern would be an existing
application that relies on data not being logged when the pty is
disconnected.
--Ed