Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <5.1.0.14.2.20010710124746.03f403b0@imap.local.mscha.com>
X-Sender: ml AT imap DOT local DOT mscha DOT com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 10 Jul 2001 12:55:20 +0200
To: Corinna Vinschen <cygwin AT cygwin DOT com>
From: Michael Schaap <cygwin AT mscha DOT com>
Subject: Re: CRON and time
In-Reply-To: <20010710122716.M8578@cygbert.vinschen.de>
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010710004537 DOT 05a224d8 AT imap DOT local DOT mscha DOT com>
 <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010628134148 DOT 03478e48 AT imap DOT mscha DOT org>
 <D8D1A6A7110BD51188B600E018C673D02D9843 AT ross DOT dorotech DOT fr>
 <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010628134148 DOT 03478e48 AT imap DOT mscha DOT org>
 <20010709121124 DOT I8578 AT cygbert DOT vinschen DOT de>
 <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010710004537 DOT 05a224d8 AT imap DOT local DOT mscha DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Virus-Scanned: at mscha.com by AMaViSd snapshot-20010407 (http://amavis.org/)

At 12:27 10-7-2001, you wrote:
>On Tue, Jul 10, 2001 at 12:59:01AM +0200, Michael Schaap wrote:
> > I just installed the new cron package (cron-3.1.0-3), but now crontab 
> dumps
> > core on me.  This happens with "crontab -e" after saving the file, and 
> with
> > "crontab filename".  "crontab -l" works fine.
>
>Thanks for the report. I think I have found the problem. My muddling
>around with the environment was good for cron but unfortunately not for
>crontab. I think I have fixed it and additionally it is less intrusive
>then my yesterday's solution. At least it doesn't crash anymore
>for me and cron still works.
>
>Are you interested to make a quick test?

Sure.

It works fine - both cron and crontab compile and run.

However, one thing is funny.  My test crontab had a command like "date >> 
/tmp/hello.txt", and that behaves slightly different with this version of cron.
When I run date from the cron-3.0.1-2 version, or when I run date from the 
command line, I get output like:
         Tue Jul 10 12:49:29  2001
But when I run it with this freshly compiled cron, I get:
         Tue Jul 10 12:49:00 T-1 2001
I guess both are incorrect, from a UNIX point of view, and the second one 
is actually a bit better than the first one...

  - Michael


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