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 Date: Wed, 17 Jul 2002 08:57:53 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Broken since 1.3.10, or earlier Message-ID: <20020717125753.GC28334@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <5.1.0.14.2.20020716164508.02e9fc30@pop3.cris.com> <20020717022743.GA24046@redhat.com> <136102275544.20020717143504@logos-m.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <136102275544.20020717143504@logos-m.ru> User-Agent: Mutt/1.3.23.1i On Wed, Jul 17, 2002 at 02:35:04PM +0400, egor duda wrote: >But that can't be the case on any unix too! Sooner or later system >reach maximum possible value of pid and will have to turn it over. It is very unlikely to happen on unix within the timeframe where it will bother bash. >Can you point where bash makes such assumptions, and probably this can >be fixed in bash? I have traced this through bash in the past enough to convince myself that it isn't cygwin's fault. However I don't remember details. If it was a simple fix I would have offered a patch. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/