From owner-freebsd-stable@FreeBSD.ORG Wed Nov 7 14:48:45 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8676316A419 for ; Wed, 7 Nov 2007 14:48:45 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by mx1.freebsd.org (Postfix) with ESMTP id 2334A13C4B5 for ; Wed, 7 Nov 2007 14:48:44 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by mu-out-0910.google.com with SMTP id i10so2638178mue for ; Wed, 07 Nov 2007 06:48:34 -0800 (PST) Received: by 10.82.106.14 with SMTP id e14mr15155187buc.1194445273056; Wed, 07 Nov 2007 06:21:13 -0800 (PST) Received: by 10.82.162.16 with HTTP; Wed, 7 Nov 2007 06:21:13 -0800 (PST) Message-ID: Date: Wed, 7 Nov 2007 16:21:13 +0200 From: "Vlad GALU" To: "Tom Evans" In-Reply-To: <1194432178.64797.42.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071106201948.GA6590@iogyte.ro> <1194432178.64797.42.camel@localhost> Cc: freebsd-stable@freebsd.org, Dan Epure Subject: Re: openpty() and jail in RELENG_7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2007 14:48:45 -0000 On 11/7/07, Tom Evans wrote: > On Tue, 2007-11-06 at 22:19 +0200, Dan Epure wrote: > > Hi All, > > > > > > I'm using on the host system (7.0-BETA2): > > #sysctl kern.pts.enable > > kern.pts.enable: 1 > > I have no problem at all. > > > > The jail is also 7.0-BETA2 > > > > The problem is inside the jail openpty() can not allocate the pty: > > === cut here === > > debug1: monitor_child_preauth: test2 has been authenticated by privileged process > > debug1: PAM: reinitializing credentials > > debug1: Entering interactive session for SSH2. > > debug1: server_init_dispatch_20 > > debug1: server_input_channel_open: ctype session rchan 0 win 65536 max 16384 > > debug1: input_session_request > > debug1: channel 0: new [server-session] > > debug1: session_new: init > > debug1: session_new: session 0 > > debug1: session_open: channel 0 > > debug1: session_open: session 0: link with channel 0 > > debug1: server_input_channel_open: confirm session > > debug1: server_input_channel_req: channel 0 request pty-req reply 0 > > debug1: session_by_channel: session 0 channel 0 > > debug1: session_input_channel_req: session 0 req pty-req > > debug1: Allocating pty. > > debug1: session_new: init > > debug1: session_new: session 0 > > openpty: No such file or directory > > session_pty_req: session 0 alloc failed > > debug1: server_input_channel_req: channel 0 request shell reply 0 > > debug1: session_by_channel: session 0 channel 0 > > debug1: session_input_channel_req: session 0 req shell > > === and here === > > the ssh session just hangs. (no pty ?) > > > > I did not forget to mount devfs inside the jail. > > The jail is configured in rc.conf: > > === cut here === > > jail_enable="YES" > > jail_list="test" > > jail_test_hostname="test.mydomain.org" > > jail_test_rootdir="/jails/test" > > jail_test_interface="bge0" > > jail_test_devfs_enable="YES" > > jail_test_ip="192.168.10.2" > > jail_set_hostname_allow="NO" > > jail_sysvipc_allow="NO" > > jail_socket_unixiproute_only="YES" > > === and here === > > I think the problem is related to restrictions imposed by the jail. > > > > Please advise. > > > > Gepu > > This is because you haven't been allocated a pty inside your jail. > Enable sshd inside your jail, ssh to your jail (which will allocate you > a pty). Then from inside your jail, you can use any pty-using > application you wish. > > I am presuming you are doing something like 'jexec 1 /bin/csh' or > similar, and I'm only really repeating Xin Li's advice to me[1]. > > Cheers > > Tom > > [1] > http://lists.freebsd.org/pipermail/freebsd-jail/2007-October/000106.html > > I'm chiming in to signal a possibly related problem. Logging in and out via sshd behaves normally (ie: the ptys are cleaned up accordingly) but opening virtual consoles in screen and then closing them does not, thus leading to starvation. -- Mahnahmahnah!