Re: cannot open tty-output

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" <eugene@home.wdc.spb.ru> wrote:
>>>>>
>>>>>> *Marco Steinbach wrote:
>>>>>> *
>>>>>>> Hi,
>>>>>>>
>>>>>>> after installing dialog4ports, I'm getting the following behaviour
>>>>>>> on each 8.3-STABLE I tried:
>>>>>>>
>>>>>>> # jexec <JID> /bin/tcsh
>>>>>>> # cd <SomePortDir>
>>>>>>> # 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
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"