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
From:	"Paul Derbyshire" <derbyshire AT globalserve DOT net>
To:	cygwin AT cygwin DOT com
Date:	Wed, 31 Jul 2002 15:46:10 -0400
MIME-Version:	1.0
Subject:	Re: Cron problem
Reply-to:	derbyshire AT globalserve DOT net
Message-ID:	<3D480642.25279.64EE3D2C@localhost>
In-reply-to:	<3D47E7EB.16325.6477B9F0@localhost>
References:	<Mahogany-0 DOT 64 DOT 2-1776-20020730-071414 DOT 00 AT MCHASE-COMPAQ>
References:	<Mahogany-0 DOT 64 DOT 2-1776-20020730-071410 DOT 00 AT MCHASE-COMPAQ>

On 31 Jul 2002 at 13:36, Paul Derbyshire wrote:

> [I should put Cygwin's bin directory on the Windows path before
> djgpp's.]
> 
> Unfortunately, that would fix cron and break djgpp. Got any more 
> suggestions?
> 
> Meanwhile I'll try setting the PATH inside the crontab...
> 
> [copies PATH="/usr/local/bin:/usr/bin:/bin:$PATH" from top line of 
> /etc/profile to top line of crontab and times job for ten minutes 
> from now]

Nevermind, that worked perfectly. The cron job ran and did what it 
was designed to do, and sent me the only pleasant email I've gotten 
so far today when it did so. :)

Would that all problems went away that easily.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -