This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

YA snapshot available [Re: new snapshot with some tty/WinMe fixes]

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

>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
>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


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]