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
Message-ID:	<217E3C0C100E144B93AF131E71C6D62A031E7AB7@edc-exchange.everdreamcorp.com>
From:	David Byron <DByron AT everdreamcorp DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	RE: event logging -- cron
Date:	Tue, 8 Apr 2003 15:28:11 -0700
MIME-Version:	1.0

On Tue, 8 April 2003, Igor Pechtchanski wrote:

> <http://cygwin.com/ml/cygwin/2003-03/msg01087.html> might help clear
things up.

It does.  Thank you.  I may get to a patch for that, but there's still the
strange return code from cron_pclose() that generates the

/usr/sbin/cron : PID 3132 : (DByron) MAIL (mailed 20 bytes of output but got
status 0xffffffff ).

part of the event.

Any ideas?  I'll let you know if I figure it out.

All the best,

-DB
--
David Byron                   dbyron AT everdream DOT com
Everdream                     http://www.everdream.com
6591 Dumbarton Circle         voice:(510)818-5550
Fremont, CA  94555            fax:(510)818-5510

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