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 To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: cron dying in Windows but not in Cygwin Date: Thu, 27 May 2004 14:50:05 +0200 Lines: 37 Message-ID: <15uzhz9jogd14.dlg@thorstenkampe.de> References: <1kaz6f74w8ele DOT dlg AT thorstenkampe DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: isi-dialin-129-165.isionline-dialin.de User-Agent: 40tude_Dialog/2.0.12.1de * Dave Korn (2004-05-27 11:26 +0100) >> * Robert Pollard (2004-05-26 18:33 +0100) >>> I have a bit of a problem where when we launch cron from >> the command >>> line after a few days it dies in Windows but is still visible in >>> Cygwin. >> >> Beg your pardon? Your sentence doesn't make sense to me. >> >>> Currently, I run a script that launches /usr/sbin/cron. This >>> script only launches cron if it isn't running. >>> >>> Does it have something to do with not launching from an rc file? >> >> Excuse me? rc files are /configuration/ files... > > Have you ever actually *read* one? They're shell scripts. You mean the runlevel scripts in rc.d? They're neither part of the default Cygwin nor of cron installation so I didn't think of these. /I/ meant "rc files" like bashrc, zshrc, etc. This misunderstanding proves only two things: 1. People who are retentive with facts and descriptions (like RP) provoke misunderstandings inevitably. 2. If RP had even a slight understanding of Cygwin, he would have known that no "runlevel script" is required to start a "Cygwin service/daemon" (because there are no Cygwin services or daemons; just Windows services.) But I'm not even sure that RP read the cron readme so 2. may be pointless. Thorsten -- 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/