From owner-freebsd-current@FreeBSD.ORG  Tue Apr 29 14:02:51 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C08B037B405
	for <freebsd-current@freebsd.org>;
	Tue, 29 Apr 2003 14:02:51 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D21F743F75
	for <freebsd-current@freebsd.org>;
	Tue, 29 Apr 2003 14:02:50 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h3TL2ls4000852;
	Tue, 29 Apr 2003 23:02:47 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Lucky Green <shamrock@cheesy.cypherpunks.to>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 29 Apr 2003 11:31:59 PDT."
             <20030429112849.T95090@cheesy.cypherpunks.to> 
Date: Tue, 29 Apr 2003 23:02:47 +0200
Message-ID: <851.1051650167@critter.freebsd.dk>
cc: freebsd-current@freebsd.org
Subject: Re: 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2003 21:02:52 -0000

In message <20030429112849.T95090@cheesy.cypherpunks.to>, Lucky Green writes:
>One of my 5.0 test boxes is spewing these cron emails. Any idea why this
>might be? (Email addresses modified)

/usr/libexec/save-entropy is a shell script and it pulls in /etc/rc.conf
and friends.  It's probably something in there that trips it...

>From: operator@example.com (Cron Daemon)
>To: operator@example.com
>Subject: Cron <operator@cheesy> /usr/libexec/save-entropy
>X-Cron-Env: <SHELL=/bin/sh>
>X-Cron-Env: <PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin>
>X-Cron-Env: <HOME=/>
>X-Cron-Env: <LOGNAME=operator>
>X-Cron-Env: <USER=operator>
>Status: O
>X-Status:
>X-Keywords:
>X-UID: 6959
>
>route: not found
>
>myhost# which route
>/sbin/route
>myhost#
>
>Thanks,
>--Lucky
>
>_______________________________________________
>freebsd-current@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.