Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-WM-Posted-At:	avacado.atomice.net; Thu, 9 May 02 22:14:20 +0100
Message-ID:	<052501c1f79e$7c4dee20$0100a8c0@advent02>
From:	"Chris January" <chris AT atomice DOT net>
To:	<cygwin AT cygwin DOT com>
References:	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020509170045 DOT 060a8530 AT lnxmain>
Subject:	Re: Processes forking on their own?
Date:	Thu, 9 May 2002 22:14:20 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

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

- Raw text -