From owner-freebsd-questions@FreeBSD.ORG Tue Jul 13 12:40:21 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 E928016A4CE for ; Tue, 13 Jul 2004 12:40:21 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E29243D2F for ; Tue, 13 Jul 2004 12:40:21 +0000 (GMT) (envelope-from freebsd-questions@m.gmane.org) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BkMa3-0005Wm-00 for ; Tue, 13 Jul 2004 14:40:19 +0200 Received: from dsl-62-3-100-125.zen.co.uk ([62.3.100.125]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Jul 2004 14:40:19 +0200 Received: from darenr by dsl-62-3-100-125.zen.co.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Jul 2004 14:40:19 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Daren Date: Tue, 13 Jul 2004 13:23:26 +0100 Lines: 18 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: dsl-62-3-100-125.zen.co.uk User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040707) X-Accept-Language: en-us, en Sender: news Subject: newsyslog bizarreness 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: Tue, 13 Jul 2004 12:40:22 -0000 Hi, I recently removed a couple of lines from newsyslog.conf, and now every hour I'm getting an email from cron telling me that newsyslog complained about the lines which are now deleted! There is definately only one config file, and if I run newsyslog from command line, it exits without a problem and running it in verbose, it doesn't see the two lines. Is there something about the cronned newsyslog that's different? Oddly, the actual error is a mis-interpretation to do with the size field (it is reading the time/date field). Any ideas on this? Thanks Daren