From owner-freebsd-questions  Tue Jun 29 14: 1: 4 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from ucsu.Colorado.EDU (ucsu.Colorado.EDU [128.138.129.83])
	by hub.freebsd.org (Postfix) with ESMTP id C4A3014EB5
	for <freebsd-questions@freebsd.org>; Tue, 29 Jun 1999 14:00:58 -0700 (PDT)
	(envelope-from doranj@ucsu.Colorado.EDU)
Received: (from doranj@localhost)
	by ucsu.Colorado.EDU (8.9.3/8.9.3/ITS-5.0/standard) id PAA09783
	for freebsd-questions@freebsd.org; Tue, 29 Jun 1999 15:00:57 -0600 (MDT)
From: Jonathon Doran <doranj@Colorado.EDU>
Message-Id: <199906292100.PAA09783@ucsu.Colorado.EDU>
Subject: Re: cron difficulties
To: freebsd-questions@freebsd.org
Date: Tue, 29 Jun 1999 15:00:57 -0600 (MDT)
In-Reply-To: <3.0.5.32.19990629110326.007ad1e0@in.mnsi.net> from "Windsor Match Plate and Tool Ltd." at Jun 29, 99 11:03:26 am
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Subject: Cron <root@wmptl> root       sh /etc/rmpopper > /dev/null 2>&1

One should always place absolute paths in a cron command.  You may not
make assumptions about the environment, like the value of $PATH for example.

Your problem may be that cron is unable to resolve "sh".  "/bin/sh" would
help in that case.

Jon Doran


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message