From owner-freebsd-stable Thu May 30 18:33: 7 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id CC4CF37B404 for ; Thu, 30 May 2002 18:33:00 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g4V1Wsp72022; Thu, 30 May 2002 18:32:54 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g4V1Wrw38438; Thu, 30 May 2002 18:32:53 -0700 (PDT) (envelope-from jdp) Date: Thu, 30 May 2002 18:32:53 -0700 (PDT) Message-Id: <200205310132.g4V1Wrw38438@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: mike@adept.org Subject: Re: ssh + X11 forwarding = a hung ssh process In-Reply-To: <20020530170501.A37186-100000@snafu.adept.org> References: <20020530170501.A37186-100000@snafu.adept.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20020530170501.A37186-100000@snafu.adept.org>, Mike Hoskins wrote: > On Thu, 30 May 2002, John Polstra wrote: > > > Nah, I don't agree with that. The ssh process should stay around as > > long as there is an X11 connection open, but it should die when the > > last tunneled X11 connection is closed (i.e., when the remote xterm > > exits). That's what it's traditionally done, and that's the more > > useful behavior. > > I see what I've always observed, > > mike@mojo{mike}$ ssh -C -X snafu.adept.org xterm > mike@snafu.adept.org's password: > > > Waiting for forwarded connections to terminate... > The following connections are open: > #1 X11 connection from snafu.adept.org port 2758 (t4 r0 i4/0 o16/0 fd 8/8) > > If you try to close the tunnel while X sessions are active, you get > alerted of the open sessions. Otherwise, as in this case, things close > normally. It only happens when protocol version 2 is used. Try forcing that with "ssh -2 ...", and there's a good chance you'll see the problem. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message