Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 15 Aug 2005 21:21:38 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Herb Martin cc: cygwin AT cygwin DOT com Subject: RE: Anyone running spfd on Cygwin? (Attn: cygrunsrv maintainer) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 11 Aug 2005, Herb Martin wrote: > > [mailto:cygwin-owner AT XXXXXX DOT XXX] On Behalf Of Brian Dessent > > Sent: Wednesday, August 10, 2005 5:45 PM > > To: cygwin AT XXXXXX DOT XXX > > Subject: Re: Anyone running spfd on Cygwin? . Thanks. > [snip] > Can a Cygwin program that is being run as a service be effectively sent > a "HUP" to get it to re-read it's configuration? > > Assumptions: That service accepts HUP and reloads its configuration > when run as a daemon. > > 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()? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- 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/