Message-ID: <4B8C9F11.2070207@monai.ca>
Date: Mon, 01 Mar 2010 21:16:01 -0800
From: Steven Monai <steve+cygwin AT monai DOT ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Feature Request:  Allow cron to terminate with SIGHUP
References: <4B8C8B52 DOT 1040503 AT columbus DOT rr DOT com>
In-Reply-To: <4B8C8B52.1040503@columbus.rr.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On 2010/03/01 7:51 PM, Paul McFerrin wrote:
[...]
> Is there a reason [for cron] to catch SIGHUP?

cron, like many UNIX daemon programs, interprets SIGHUP as a signal to
close and reopen its log file. This is typically used to facilitate log
file rotation. It is quite unlikely that cron's maintainer would want to
change this.

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

If you're not using cron for anything, you should probably just stop and
permanently remove the service, e.g.:

$ cygrunsrv -E cron
$ cygrunsrv -R cron

If you are using cron for something, then you'll have to remember to
stop the cron service whenever you want/need to shut down all cygwin
processes, e.g.:

$ cygrunsrv -E cron

This can get tedious if you have a number of cygrunsrv services
installed. Here is a little bash script that should stop them all:

#!/bin/bash
cygrunsrv -L |
while read service; do
    cygrunsrv -E "$service"
done

Hope this helped,
-SM
--

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