From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LwJ9w-0000Ss-EG
	for qemu-devel@nongnu.org; Tue, 21 Apr 2009 12:49:24 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LwJ9r-0000Sg-Rh
	for qemu-devel@nongnu.org; Tue, 21 Apr 2009 12:49:24 -0400
Received: from [199.232.76.173] (port=47732 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LwJ9r-0000Sd-P2
	for qemu-devel@nongnu.org; Tue, 21 Apr 2009 12:49:19 -0400
Received: from mx20.gnu.org ([199.232.41.8]:26598)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <anthony@codemonkey.ws>)
	id 1LwJ9r-0007FD-Cb
	for qemu-devel@nongnu.org; Tue, 21 Apr 2009 12:49:19 -0400
Received: from mail-gx0-f176.google.com ([209.85.217.176])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1LwJ9q-0005nZ-4E
	for qemu-devel@nongnu.org; Tue, 21 Apr 2009 12:49:18 -0400
Received: by gxk24 with SMTP id 24so5380323gxk.10
	for <qemu-devel@nongnu.org>; Tue, 21 Apr 2009 09:49:17 -0700 (PDT)
Message-ID: <49EDF907.5030100@codemonkey.ws>
Date: Tue, 21 Apr 2009 11:49:11 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] resetting a stale VNC connection
References: <49EDC3B4.7030508@cisco.com> <49EDCC6F.1020703@redhat.com>
	<20090421164023.GE26731@redhat.com>
In-Reply-To: <20090421164023.GE26731@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, "David S. Ahern" <daahern@cisco.com>, qemu-devel@nongnu.org

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
>