Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Anyone running spfd on Cygwin? (Attn: cygrunsrv maintainer)
Date: Tue, 16 Aug 2005 13:16:28 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.GSO.4.61.0508152105560.9560@slinky.cs.nyu.edu>
Message-ID: <SERRANOpwACkWHZqYW80000004f@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Igor Pechtchanski
>Sent: 16 August 2005 02:22

> On Thu, 11 Aug 2005, Herb Martin wrote:
>> Or must such services be stopped and restarted completely?
> 
> Yes, but you'll need to send SIGHUP to the program process, and not to the
> corresponding cygrunsrv process, since, IIRC, cygrunsrv itself will
> unconditionally terminate the child daemon on SIGHUP (and SIGTERM, and
> SIGQUIT, and SIGINT).
> 
> Corinna, perhaps cygrunsrv should pass explicit SIGHUPs to the child
> instead (unless --termsig is HUP)?  Or, better yet, pass the signal to
> send as an argument to terminate_child()?

  I think that if someone wants to send a signal to the child, they should
send it to the child, and if someone wants to send a signal to the parent,
they should send it to the parent, and I don't think cygrunsrv should try to
second guess them.

  And stop calling me Corinna!


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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