From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, "David S. Ahern" <daahern@cisco.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] resetting a stale VNC connection
Date: Tue, 21 Apr 2009 11:49:11 -0500 [thread overview]
Message-ID: <49EDF907.5030100@codemonkey.ws> (raw)
In-Reply-To: <20090421164023.GE26731@redhat.com>
Daniel P. Berrange wrote:
> On Tue, Apr 21, 2009 at 04:38:55PM +0300, Avi Kivity wrote:
>
>> David S. Ahern wrote:
>>
>>> Is there a monitor command (or other method) to force a VNC client
>>> connection to close?
>>>
>>> It looks like the vnc code does not use keepalive probes. If the
>>> connection is left hanging the VNC server will never drop it. I have hit
>>> this condition a couple of times when a VPN connection drops while the
>>> vncviewer is connected to a VM.
>>>
>>> Specific software version at the moment is kvm-81.
>>>
>>>
>> Why not just enable tcp keepalives?
>>
>
> Independant of killing off stale VNC clients, it could be desirable to
> have a monitor command to kill a client, to allow revoking of end user
> access to VNC.
>
I'm surprised change vnc none doesn't kill off all VNC connections.
I don't see a compelling use case to boot off individual clients other
than we can. Is there something specific you were thinking someone
would want to do?
Regards,
Anthony Liguori
> Daniel
>
next prev parent reply other threads:[~2009-04-21 16:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 13:01 [Qemu-devel] resetting a stale VNC connection David S. Ahern
2009-04-21 13:38 ` Avi Kivity
2009-04-21 15:10 ` David S. Ahern
2009-04-21 16:12 ` Avi Kivity
2009-04-21 16:19 ` Yaniv Kaul
2009-04-21 16:28 ` David S. Ahern
2009-04-21 16:33 ` Avi Kivity
2009-04-21 18:33 ` David Ahern
2009-04-21 18:38 ` Avi Kivity
2009-04-21 16:38 ` Yaniv Kaul
2009-04-21 16:40 ` Daniel P. Berrange
2009-04-21 16:49 ` Anthony Liguori [this message]
2009-04-21 17:17 ` Daniel P. Berrange
2009-04-21 19:30 ` David S. Ahern
2009-04-21 19:32 ` Anthony Liguori
2009-04-22 8:18 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49EDF907.5030100@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=daahern@cisco.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).