From owner-freebsd-ports@FreeBSD.ORG Mon Mar 25 10:42:53 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7D42FA06 for ; Mon, 25 Mar 2013 10:42:53 +0000 (UTC) (envelope-from coco@executive-computing.de) Received: from mail.moehre.org (mail.moehre.org [195.96.35.7]) by mx1.freebsd.org (Postfix) with ESMTP id 17258E98 for ; Mon, 25 Mar 2013 10:42:52 +0000 (UTC) Received: from mail.moehre.org (unknown [195.96.35.7]) by mail.moehre.org (Postfix) with ESMTP id 5756A8B1420; Mon, 25 Mar 2013 11:42:52 +0100 (CET) X-Spam-Flag: NO X-Spam-Score: -100.076 X-Spam-Level: X-Spam-Status: No, score=-100.076 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, AWL=-0.851, URIBL_BLACK=1.775, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mail.moehre.org ([195.96.35.7]) by mail.moehre.org (mail.moehre.org [195.96.35.7]) (amavisd-new, port 10024) with ESMTP id ZsVdH5PKTgK8; Mon, 25 Mar 2013 11:42:50 +0100 (CET) Received: from [192.168.100.30] (p54B0A677.dip.t-dialin.net [84.176.166.119]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: coco@executive-computing.de) by mail.moehre.org (Postfix) with ESMTPSA id 63F3E8B143B; Mon, 25 Mar 2013 11:42:50 +0100 (CET) Message-ID: <51502A4A.4080604@executive-computing.de> Date: Mon, 25 Mar 2013 11:43:22 +0100 From: Marco Steinbach User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: "Ilya A. Arkhipov" Subject: Re: cannot open tty-output References: <514F56BF.5040805@home.wdc.spb.ru> <20130324215847.2243e4dc@bsd64.grem.de> <514F8E36.3010606@executive-computing.de> <51501192.30303@home.wdc.spb.ru> <51502087.40108@executive-computing.de> <515022BA.6020201@rambler-co.ru> In-Reply-To: <515022BA.6020201@rambler-co.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org, eugene@wdc.spb.ru X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Mar 2013 10:42:53 -0000 Ilya A. Arkhipov wrote on 25.03.2013 11:11: > On 03/25/13 14:01, Marco Steinbach wrote: >> Eugene V. Boontseff wrote on 25.03.2013 09:57: >>> On 25.03.2013 03:37, Marco Steinbach wrote: >>>> Michael Gmelin schrieb: >>>>> On Sun, 24 Mar 2013 23:40:47 +0400 >>>>> "Eugene V. Boontseff" wrote: >>>>> >>>>>> *Marco Steinbach wrote: >>>>>> * >>>>>>> Hi, >>>>>>> >>>>>>> after installing dialog4ports, I'm getting the following behaviour >>>>>>> on each 8.3-STABLE I tried: >>>>>>> >>>>>>> # jexec /bin/tcsh >>>>>>> # cd >>>>>>> # make config >>>>>>> >>>>>>> cannot open tty-output >>>>>>> ===> Options unchanged >>>>>>> # >>>>>>> >>>>>>> Regardless, if I'm logged in on the console or connect to the host >>>>>>> via ssh. >>>>>>> >>>>>>> >>>>>>> I've also tried on 8.4-BETA1 (r248617), but got the same behaviour. >>>>>>> >>>>>>> Anyone else experiencing this ? >>>>>> Yes, I have also experienced this. >>>>>> 8.3-STABLE r244863 >>>>>> Only if i do a "make config" in a jail. >>>>>> Outside the jail all goes well. >>>>>>> MfG CoCo >>>>> >>>>> This problem doesn't exist in 9.1. On 8 it only happens when you >>>>> jexeced into the jail (ssh should be ok). As a workaround you can run >>>>> tmux (sysutils/tmux) within your jail and install ports from within >>>>> the >>>>> terminal multiplexer (screen will do as well, but is also heavier). >>>>> >>>> >>>> dialog4ports(1) uses stdout for passing back results, where the >>>> former dialog(1) used stderr. I reverted the new behaviour back to >>>> the previous one, which fixed the problem for me. I don't know >>>> about other implications, though. >>>> >>>> Ilya (author of dialog4ports) is aware of the problem and having a >>>> look at it. >>>> >>>> I'm glad that other people are running into this, also. I was >>>> beginning to think, that there's something fundamentally wrong with >>>> the way our 8.x jails are configured. >>> What could it be? I configure jail with ezjail. Nothing special.. :-) >>> >>>> MfG CoCo >>> >>> >> >> Same here. With and without ezjail, same behaviour on all 8.x >> machines I tried. >> >> Using a serial console on a 9.1 machine yields the same behaviour when >> jexec is used, while there's no error when connected per ssh. >> >> MfG CoCo [...] > Hi All, > > Fixed in > https://bitbucket.org/m1cro/d4p/commits/42e03ab186b30120fa79e2d0a6093a3c673385ef > > Thanks Marco. > > After checking it will committed, but you already can test it: > - change dialog4ports version to 0.1.2 > - make makesum > - portmaster -d /usr/ports/ports-mgmt/dialog4ports > - add 2(stderr) in Tools/scripts/dialog4ports.sh in "exec $DIALOG4PORTS > 2> $OPTIONSFILE" line. > - test it :) > Tried it on 9.1 and 8.3, both with jexec using a serial console and jexec from a ssh connection. Works as advertised. Thank you for fixing this, Ilya :) MfG CoCo