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
Date: Wed, 26 Jun 2002 12:39:53 -0400
From: upat54wo AT aol DOT com
To: drobinow AT dayton DOT adroit DOT com, cygwin AT cygwin DOT com
Subject: Re: crontab -e problem
Message-ID: <31FAEA60.6425E801.00AC0A81@aol.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Thanks for straightening out my thinking, David. 

With all the warnings and disclaimers, however, I am uncomfortable with applying the snapshot because it might cause more problems than I need in a production environment.  And cron itself is working - driving a very important function every 15 minutes at the moment.

Guess I have to wait for an offical release...

David 

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