X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.3 required=5.0 tests=AWL,BAYES_00
X-Spam-Check-By:	sourceware.org
X-Authority-Analysis:	v=1.0 c=1 a=W9LNM46SgAsA:10 a=1W77UtOIW7UBkzPmJEsA:9 a=ajrc0OwGR00az9zHS9PQXyQxkn0A:4
Message-ID:	<4B8C8B52.1040503@columbus.rr.com>
Date:	Mon, 01 Mar 2010 22:51:46 -0500
From:	Paul McFerrin <pmcferrin AT columbus DOT rr DOT com>
Reply-To:	pmcferrin AT columbus DOT rr DOT com
User-Agent:	Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version:	1.0
To:	Cygwin <cygwin AT cygwin DOT com>
Subject:	Feature Request: Allow cron to terminate with SIGHUP
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

With every Cygwin session I have two windows opened:  One CONSOLE and 
the other a miscelanious windon running rxvt.  When I want to shut down 
Cygwin and it's web servers, I just exit the console window.  When I 
exit the console window, every process gets terminated with SIGHUP.  No 
exceptions get terminated until now.  The cron command is ignoring 
SIGHUP and thus causes extra stuff to be done to perform a gracefull 
shutdown.

Is there a reason to catch SIGHUP?  I would like to keep my running of 
cygwin.  I knew something changed, now I know.  With cron running all 
the time, it is more difficult to unload cygwin1.dll.

- Paul

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -