OpenSSH
[Top] [All Lists]

Re: ControlPersist and multiple X11 forwarding.

To: John Davidorff Pell <johnpell@mac.com>
Subject: Re: ControlPersist and multiple X11 forwarding.
From: David Woodhouse <dwmw2@infradead.org>
Date: Tue, 30 Jan 2007 14:09:32 +0000
Cc: openssh-unix-dev@mindrot.org
Delivered-to: sp-com-lists@consult.net
Delivered-to: openssh-unix-dev-list1@securepoint.com
Delivered-to: openssh-unix-dev-tmda@mindrot.org
Delivered-to: openssh-unix-dev@mindrot.org
In-reply-to: <841AFCF9-4872-407C-89B6-DA39C8B15B07@mac.com>
List-archive: <http://lists.mindrot.org/pipermail/openssh-unix-dev>
List-help: <mailto:openssh-unix-dev-request@mindrot.org?subject=help>
List-id: Development of portable OpenSSH <openssh-unix-dev.mindrot.org>
List-post: <mailto:openssh-unix-dev@mindrot.org>
List-subscribe: <http://lists.mindrot.org/mailman/listinfo/openssh-unix-dev>, <mailto:openssh-unix-dev-request@mindrot.org?subject=subscribe>
List-unsubscribe: <http://lists.mindrot.org/mailman/listinfo/openssh-unix-dev>, <mailto:openssh-unix-dev-request@mindrot.org?subject=unsubscribe>
References: <841AFCF9-4872-407C-89B6-DA39C8B15B07@mac.com>
Sender: openssh-unix-dev-bounces+openssh-unix-dev-list1=securepoint.com@mindrot.org
On Mon, 2007-01-29 at 13:40 -0800, John Davidorff Pell wrote:
> After searching the archives, I came up with this thread  
> "ControlPersist and multiple X11 forwardings." However, I can't find  
> anything saying that it was incorporated or not, or what has  
> happened. The last reply to this thread was in 2005.

Bits of it were incorporated but other parts are still outstanding.
I build my own packages for Fedora Core with the remaining bits applied.

http://david.woodhou.se/openssh-control.html has the patches, although
the packages linked from there are old -- the current packages are at
ftp://ftp.infradead.org/pub/dwmw2-fc6/

> Unlike the originator of the thread, I don't have a patch to offer,  
> only a request to make:
> 
> I would find the ControlPersist option very useful, but I would find  
> a slight alteration even more useful: an option to background the  
> "master" process *so long as there are open channels*. I don't want  
> an open ssh connection just hanging around, but I also don't like an  
> extra, useless xterm left open doing nothing at all while another  
> window has something going.

Would you settle for a timeout -- letting the master background itself
but then disconnect after a period of inactivity which you can configure
as low as you like, and which I can set to infinite?

-- 
dwmw2

_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@mindrot.org
http://lists.mindrot.org/mailman/listinfo/openssh-unix-dev

<Prev in Thread] Current Thread [Next in Thread>