| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-SWARE-Spam-Status: | No, hits=-1.9 required=5.0 tests=AWL,BAYES_05 |
| X-Spam-Check-By: | sourceware.org |
| X-Cloudmark-SP-Filtered: | true |
| X-Cloudmark-SP-Result: | v=1.0 c=1 a=92HjQVi3oQkA:10 a=kCKDY91tEBMc+hi4YtGk8Q==:17 a=gTQ0MIiqk7PdGkJf1MwA:9 a=sGE06z44Dzkb4ypW0vQA:7 a=X0csMsFSVtQC52VccWod1lcrISYA:4 |
| 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> |
| 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 |
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
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |