Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Reply-To:	Cygwin List <cygwin AT cygwin DOT com>
Message-Id:	<6.1.0.6.0.20041103202747.041a5ac0@pop.prospeed.net>
X-Sender:
Date:	Wed, 03 Nov 2004 20:30:04 -0500
To:	Simon Buchanan <nmc AT orcon DOT net DOT nz>, cygwin AT cygwin DOT com
From:	Larry Hall <lh-no-personal-replies-please AT cygwin DOT com>
Subject:	Re: cron event error message
In-Reply-To:	<4189619F.5080605@orcon.net.nz>
References:	<4189619F DOT 5080605 AT orcon DOT net DOT nz>
Mime-Version:	1.0

At 05:54 PM 11/3/2004, you wrote:
>/USR/SBIN/CRON : PID 788 : (Administrator) MAIL (mailed 65 bytes of output but got status 0x0001
>).


This is the operative part.  I think it's fairly self-explanatory, in terms
of what happened.  You might take a gander at '/var/log/cron.log' for 
additional hints if that's not enough.  But really, this just means cron
tried to send email and it failed.  You'll have to dig a little more to 
figure out where and why.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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