From owner-freebsd-stable@FreeBSD.ORG Sun Apr 17 07:48:29 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 735A016A4CE for ; Sun, 17 Apr 2005 07:48:29 +0000 (GMT) Received: from mail20.syd.optusnet.com.au (mail20.syd.optusnet.com.au [211.29.132.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80AED43D1D for ; Sun, 17 Apr 2005 07:48:28 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j3H7mNXP013881 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 17 Apr 2005 17:48:23 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j3H7mM7l009737; Sun, 17 Apr 2005 17:48:22 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j3H7mMZm009736; Sun, 17 Apr 2005 17:48:22 +1000 (EST) (envelope-from pjeremy) Date: Sun, 17 Apr 2005 17:48:22 +1000 From: Peter Jeremy To: Andrew Reilly Message-ID: <20050417074822.GU89047@cirb503493.alcatel.com.au> References: <20050414030436.GA96739@gurney.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050414030436.GA96739@gurney.reilly.home> User-Agent: Mutt/1.4.2i cc: stable@freebsd.org cc: bugs@bugs.au.freebsd.org Subject: Re: [bugs] Misleading security message output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2005 07:48:29 -0000 On Thu, 2005-Apr-14 13:04:36 +1000, Andrew Reilly wrote: [Unexpected failed login reports in security messages] > >After much hunting around, and checking perimeter logs, it >turned out that nothing of the sort had happened. The security >log script had been fooled by the age of the messages.0.gz file, >which contained messages from more than a year ago. I was bitten at home and worked out what happened. So when the same problem showed up at work, I knew what had happened. > It can be worked-around by forcing faster log-file rotations, That's the solution I used. -- Peter Jeremy