Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <052501c1f79e$7c4dee20$0100a8c0@advent02>
From: "Chris January" <chris@atomice.net>
To: <cygwin@cygwin.com>
References: <5.1.0.14.2.20020509170045.060a8530@lnxmain>
Subject: Re: Processes forking on their own?
Date: Thu, 9 May 2002 22:14:20 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> Some of my shell scripts on Windows 2000 Server (NTFS partition) seem to
be forking their commands.
> This has the effect of everything in a script trying to run at once, which
royally screws up dependencies.  This seems to only happen sometimes.  All
in all, general system behavior is bad.
Well in a script shells will always use either fork or spawn to launch other
commands. Do you mean that the shell isn't waiting for the command to
finish?

>
> Worse yet and perhaps unrelated: when starting a process which forks
itself, when the controlling window closes, that process dies too (pg_ctl
start).  I can't seem to keep my database up unless i avoid using pg_ctl.
SIGHUP related? If you close the controlling window, SIGHUP will get sent to
the forked children. If they don't catch the signal, they will die.

Regards
Chris


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