Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID:	<005a01c14c8c$f535ca00$01000001@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	<cygwin-developers AT cygwin DOT com>
Subject:	daemon...
Date:	Thu, 4 Oct 2001 14:27:57 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

I've gotten the daemon able to track process's and fire off callback
procedures when a process quits. (Well not quite, I've got the tracking
and detection ok, had to take a brak then).

Annnyway, the point of this is that when a abnormal termination takes
place - (say) a shm attached process sigv'ing, the daemon can notice and
correct it's data structure - or shared ones. Using this example, the
nattach count needs to be decremented. Other possibilities include FIFO
reader/writer count management/removing unix socket files..

There may be more opportunities than that. This is something I hadn't
put up as a goal, cause I wasn't sure how hard it would turn out to be.

Anyway, I've also added a '(no)daemon' environment variable, which can
default to no, to allow a zero-impact period when the daemon is off by
default. (or even for specific builds).

Rob

- Raw text -