X-Spam-Check-By: sourceware.org
Date: Tue, 3 Oct 2006 10:47:17 -0400 (EDT)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.21 Forked background processes
In-Reply-To: <4522664E.30106@cygwin.com>
Message-ID: <Pine.GSO.4.63.0610031045460.23682@access1.cims.nyu.edu>
References: <loom DOT 20061002T215900-610 AT post DOT gmane DOT org> <4521AE57 DOT 9020007 AT cygwin DOT com>  <loom DOT 20061003T050921-722 AT post DOT gmane DOT org> <4522664E DOT 30106 AT cygwin DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Tue, 3 Oct 2006, Larry Hall (Cygwin) wrote:

> Steve wrote:
> > Larry Hall (Cygwin <reply-to-list-only-lh <at> cygwin.com> writes:
> >
> > > > file1.sh:
> > > > -----------------------------------------------
> > > > #!/usr/bin/bash
> > > >
> > > > ./file2.sh &
> > > >
> > > > ------------------------------------------------
> > > >
> > > > file2.sh
> > > > ------------------------------------------------
> > > > #!/usr/bin/bash
> > > >
> > > > while [ 1 ]
> > > > do
> > > >      val=`echo $val`
> > > >      val=$((val + 1))
> > > >      echo $val
> > > > done
> > > > ------------------------------------------------
> >
> > Thanks for your response. I'm still running into this with 1.5.21. The
> > background process has to be ran from a script, as in the example I provided
> > above. If you kick the script from the command line, this problem does not
> > occur. If you run the example above with ./file1.sh, you should see the
> > problem. I didn't run into this with DLL version 1.5.18. Here is the bash
> > and DLL versions of both:
> >
> > Problem DLL and Bash versions:
> >
> > $ bash --version
> > GNU bash, version 3.1.17(8)-release (i686-pc-cygwin)
> > Copyright (C) 2005 Free Software Foundation, Inc.
> >
> >     Cygwin DLL version info:
> >         DLL version: 1.5.21
> >         DLL epoch: 19
> >         DLL bad signal mask: 19005
> >         DLL old termios: 5
> >         DLL malloc env: 28
> >         API major: 0
> >         API minor: 156
> >         Shared data: 4
> >         DLL identifier: cygwin1
> >         Mount registry: 2
> >         Cygnus registry name: Cygnus Solutions
> >         Cygwin registry name: Cygwin
> >         Program options name: Program Options
> >         Cygwin mount registry name: mounts v2
> >         Cygdrive flags: cygdrive flags
> >         Cygdrive prefix: cygdrive prefix
> >         Cygdrive default prefix:
> >         Build date: Sun Jul 30 14:21:47 EDT 2006
> >         Shared id: cygwin1S4
> > ////////////////////////////////////////////////////
> >  No Problem DLL and Bash versions:
> >
> > $ bash --version
> > GNU bash, version 3.00.16(11)-release (i686-pc-cygwin)
> > Copyright (C) 2004 Free Software Foundation, Inc.
> >
> >
> >     Cygwin DLL version info:
> >         DLL version: 1.5.18
> >         DLL epoch: 19
> >         DLL bad signal mask: 19005
> >         DLL old termios: 5
> >         DLL malloc env: 28
> >         API major: 0
> >         API minor: 132
> >         Shared data: 4
> >         DLL identifier: cygwin1
> >         Mount registry: 2
> >         Cygnus registry name: Cygnus Solutions
> >         Cygwin registry name: Cygwin
> >         Program options name: Program Options
> >         Cygwin mount registry name: mounts v2
> >         Cygdrive flags: cygdrive flags
> >         Cygdrive prefix: cygdrive prefix
> >         Cygdrive default prefix:
> >         Build date: Sat Jul 2 20:30:04 EDT 2005
> >         Shared id: cygwin1S4
> > //////////////////////////////////////////////////////
> >
> > I also tried Bash 3.00.16(11) with DLL version 1.5.21 and still had a
> > problem. I see this on several machines so it's not isolated to one.
> >
> > Thanks for your help and any info you can provide,
>
>
> I have tried this locally with 1.5.21 and bash 3.1.17-8 using the
> scripts you provided and don't see the issue you report.  That's not to
> say that there isn't an issue.  Only that I cannot reproduce it.  Maybe
> it's worthwhile for you to review the output of 'cygcheck -srv' and see
> if something there catches your attention.  If not, sending it to the
> list might spot something.

Steve,

Are you running any sort of firewall or antivirus software?  If so, it may
be hanging on to the file/memory region handles past the timeout period,
and Cygwin is unable to dispose of them.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

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