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 Date: Fri, 16 Jan 2004 13:30:44 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: YA snapshot available [Re: new snapshot with some tty/WinMe fixes] Message-ID: <20040116183044.GA24127@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <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 Content-Disposition: inline In-Reply-To: <3.0.5.32.20040103181628.00835c70@incoming.verizon.net> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com 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. I haven't seen a popup in Windows Me for some time with the latest snapshot and I've been able to configure/make cygwin under ME with no problem. >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)." This should be ok now. >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 This also should be working now. >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). I was hoping that Corinna would chime in here but maybe she isn't following this discussion. IIRC, I resisted adding the open_fhs checks to the pty/tty handling early on but eventually was convinced that they were needed. Previously, it was pretty hard to have a program with handles to more than one console but, with the existence of the "new" windows station stuff it is conceivable, if unlikely that a program could have two open. In that context the open_fhs stuff is being overused, but that was part of the motivation for implementing the new archetype stuff in the DLL -- then I can eventually get rid of the open_fhs stuff in favor of setting up console archetypes. There is still a lot of genericizing to do to accommodate that but it is a future goal. cgf -- 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/