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
To: cygwin AT cygwin DOT com
From: Thorsten Kampe <thorsten AT thorstenkampe DOT de>
Subject: Re: cron problem report
Date: Mon, 1 Mar 2004 22:37:51 +0100
Lines: 22
Message-ID: <1xx6tco7g0748.dlg@thorstenkampe.de>
References: <40439C97 DOT 20903 AT gmu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: isi-dialin-129-42.isionline-dialin.de
User-Agent: 40tude_Dialog/2.0.10.1de

* Seiji Tokunaga (2004-03-01 21:27 +0100)
> I have trouble getting my cron to work.

Please consider explaining what you mean by this otherwise any answer
to your report won't satisfy you.

> % crontab -l
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (/tmp/crontab.3928 installed on Mon Mar  1 15:03:19 2004)
> # (Cron version -- $Id: crontab.c,v 1.7 2003/04/15 15:13:41 corinna Exp $)
> * * * * * `date` >> ${HOME}/foo.log

This "script" (`date` >> ${HOME}/foo.log) doesn't even work in a plain
shell so for sure not in cron. Read /var/cron/log, the system and
application entries in the eventviewer and the mail that cron probably
sent you in ~/dead.letter.

Hint: use executables with full path in crontab or set PATH in
crontab. Don't take for granted that the normal environment variables
are set ($HOME) and consider reading the man page of crontab.

Thorsten


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