From: "Daniel P. Berrange" <berrange@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, "David S. Ahern" <daahern@cisco.com>
Subject: Re: [Qemu-devel] resetting a stale VNC connection
Date: Tue, 21 Apr 2009 17:40:23 +0100 [thread overview]
Message-ID: <20090421164023.GE26731@redhat.com> (raw)
In-Reply-To: <49EDCC6F.1020703@redhat.com>
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.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-04-21 16:40 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 [this message]
2009-04-21 16:49 ` Anthony Liguori
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=20090421164023.GE26731@redhat.com \
--to=berrange@redhat.com \
--cc=avi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.