Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning:	localhost.localdomain: ronald owned process doing -bs
Date:	Wed, 4 Jun 2003 09:53:05 +0200 (CEST)
From:	Ronald Landheer-Cieslak <ronald AT landheer DOT com>
X-X-Sender:	ronald AT localhost DOT localdomain
To:	cygwin AT cygwin DOT com
Subject:	Re: Slight patch for Cron
In-Reply-To:	<20030603183428.GM875@cygbert.vinschen.de>
Message-ID:	<Pine.LNX.4.44.0306040945510.14403-100000@localhost.localdomain>
MIME-Version:	1.0

On Tue, 3 Jun 2003, Corinna Vinschen wrote:
> On Tue, Jun 03, 2003 at 06:44:19PM +0200, Ronald Landheer-Cieslak wrote:
> > On Tue, 3 Jun 2003, Ronald Landheer-Cieslak wrote:
> > > On Tue, 3 Jun 2003, Corinna Vinschen wrote:
> > > > On Tue, Jun 03, 2003 at 10:31:05AM +0200, Ronald Landheer-Cieslak wrote:
> > > > > I've "developed" an insignificant patch to cron (attached) that makes
> > > > > cron detach from the console before forking out (under Cygwin only).
> > > > > The patch is against the current release's source and WFM.
> > > > Did you try a recent developers snapshot?  This should be accomplished
> > > > by the setsid call in the child (right after fork).
> > > Assuming you mean a Cygwin snapshot, I hadn't though it was a Cygwin 
> > > problem so I haven't tried a snapshot, no, but come to think of it, the 
> > > daemonizing cron does should detach it from the console ... 
> > > 
> > > (running chin ... lol ... slap forehead)
> > > 
> > > I'll reinstall the unpatched cron, download the snapshot and give it a go. 
> > > I'll let you know.
> > Nope..
> > 
> > I've just rebooted with the latest snapshot and have a cron window hanging 
> > around. Cygcheck output is attached..
> Does it help to set CYGWIN=notty before starting cron?
Apparently not, no.

Because I'm starting cron from the "startup" part of the start menu, I had 
to run it from a batch file (
set CYGWIN=notty
cron.exe
) but I don't think that should make a difference.

rlc



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

- Raw text -