From owner-freebsd-questions@FreeBSD.ORG Mon Jul 19 17:11:17 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C57416A4CE for ; Mon, 19 Jul 2004 17:11:17 +0000 (GMT) Received: from mtiwmhc12.worldnet.att.net (mtiwmhc12.worldnet.att.net [204.127.131.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D9D243D53 for ; Mon, 19 Jul 2004 17:11:17 +0000 (GMT) (envelope-from duanewinner@worldnet.att.net) Received: from [10.10.100.99] (unknown[216.113.237.21]) by worldnet.att.net (mtiwmhc12) with ESMTP id <200407191711031120072hd7e> (Authid: duanewinner); Mon, 19 Jul 2004 17:11:03 +0000 Message-ID: <40FC00AF.8010807@att.net> Date: Mon, 19 Jul 2004 13:11:11 -0400 From: Duane Winner User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040716 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <40FBF73E.4030305@att.net> <20040719163439.GF41912@dan.emsphone.com> In-Reply-To: <20040719163439.GF41912@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: save-entropy cronjob "Added: not found" every 10 minutes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2004 17:11:17 -0000 Thanks! Using your technique, I discovered that I stupidly forgot to put a '#' before one of my comments in /etc/rc.conf. Dan Nelson wrote: > In the last episode (Jul 19), Duane Winner said: > >>Does anybody know what is going on with the cronjob >>/usr/libexec/save-entropy that by default is scheduled to run every >>10 minutes? >> >>I'm getting tons of log mail because of this, but I don't want to >>just comment out the cronjob because it is annoying. > > >>Subject: Cron /usr/libexec/save-entropy >> >>Added: not found > > > Try changing the top line of that script to read > > #!/bin/sh -x > > , which will log every command that it runs to stderr. You should then > be able to determine which line is printing that error message. My > guess is something in your rc.conf is doing it. >