Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-Id: <3.0.5.32.20031226222751.00803100@incoming.verizon.net> X-Sender: vze1u1tg@incoming.verizon.net Date: Fri, 26 Dec 2003 22:27:51 -0500 To: cygwin@cygwin.com From: "Pierre A. Humblet" Subject: Re: Please try the latest snapshot -- it is close to cygwin 1.5.6 In-Reply-To: <20031227024010.GB25085@redhat.com> References: <3.0.5.32.20031226211336.00804140@incoming.verizon.net> <20031226204641.GA46362839@hpn5170x> <20031224152951.GA34487383@hpn5170x> <20031223222816.GA23935@redhat.com> <20031224152951.GA34487383@hpn5170x> <3.0.5.32.20031224181524.007c21c0@incoming.verizon.net> <20031224232759.GA12748@redhat.com> <20031226204641.GA46362839@hpn5170x> <3.0.5.32.20031226211336.00804140@incoming.verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 09:40 PM 12/26/2003 -0500, Christopher Faylor wrote: > >I tried the current CVS version and I don't see any stray tty garbage >with inetd. I never tried this with an older snapshot, however, so I >don't know if I would have been lucky before. I did try a much simpler >test case which worked incorrectly with CYGWIN=tty and correctly after >today's initial setsid change. Here both exim and inetd are still off, with CYGWIN_ME-4.90 hpn5170x 1.5.6(0.108/3/2) 2003-12-26 22:04 i686 unknown unknown Cygwin The trace of sh -c inetd in on http://mysite.verizon.net/phumblet/trace The problem is the same, AFAICS there is an unaccounted for jump in usecount. 177 298078 [main] SH 480747 fhandler_tty_slave::open: /dev/tty0 opened, incremented open_fhs 4, archetype usecount 4 178 336409 [main] sh 480747 fhandler_tty_slave::dup: incremented open_fhs 5, archetype usecount 6 The trace also shows e.g. open_fhs -3 Still waiting for exim to misbehave. 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/