Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <3.0.5.32.20040103191807.00839100@incoming.verizon.net> X-Sender: vze1u1tg AT incoming DOT verizon DOT net Date: Sat, 03 Jan 2004 19:18:07 -0500 To: cygwin AT cygwin DOT com From: "Pierre A. Humblet" Subject: Re: new snapshot with some tty/WinMe fixes In-Reply-To: <20040103232502.GA8786@redhat.com> References: <3 DOT 0 DOT 5 DOT 32 DOT 20040103181628 DOT 00835c70 AT incoming DOT verizon DOT net> <20040103181903 DOT GA9424 AT redhat DOT com> <3 DOT 0 DOT 5 DOT 32 DOT 20040103181628 DOT 00835c70 AT incoming DOT verizon DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 06:25 PM 1/3/2004 -0500, Christopher Faylor wrote: >On Sat, Jan 03, 2004 at 06:16:28PM -0500, Pierre A. Humblet wrote: >>1) With the snapshot I can start cygwin programs fine and I have not observed >>any popup. > >Wish I could say the same. I am seeing the popup consistently. At least now I >can duplicate it. I even understand it. > >>2) The regression repeated before (see original mail for more details) is still there: >>"However when using sh, >> setsid sh -c "echo hello > /dev/tty1; /bin/sleep 10; /bin/echo there > /dev/tty" >> sh and the final echo hang forever (with echo in the "O" state in ps), >> and sh cannot be terminated with kill (OK from the task manager)." > >I could be wrong but I don't recall saying that I'd fixed that problem. You are right, you said: "I tried all of the test cases that Pierre previously reported but I'm sure I missed one." So I looked for the one. >>3) There is another regression that I had also observed with the previous snapshot, >>but after sending my previous message: the Console is not properly freed after >>setsid when CYGWIN=notty. Programs such as inetd do not go in the background when >>starting from a command.com window or from the Windows "run" menu. >>Things are fine with CYGWIN=tty > >"Go in the background" == ? If you type "setsid sleep 10" in command.com, you get the prompt back immediately when CYGWIN=tty, but you have to wait 10 s if CYGWIN=notty. If you execute inetd from "Run", the window stays around. >>By the way, I don't understand why open_fhs is modified in the slave tty and ctty >>code. The only purpose I see in open_fhs is to free the console at the right time. >>Why should the presence of a slave tty, possibly connected to an entirely different >>console window, impact on the local console? (this is not a new issue). > >You're right. This is not a new issue. It's even been discussed before. I don't >know if it was in private email between me and Corinna but since you apparently >haven't searched for any past discussion, I'll be lazy and assume it was >discussed in cygwin-developers. According to the Changelog it was probably done in early March 2003 but I didn't find any relevant discussion around that date. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/