From owner-freebsd-stable@FreeBSD.ORG Mon Apr 18 20:36:05 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 F0BB816A4CE for ; Mon, 18 Apr 2005 20:36:05 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9B2A43D53 for ; Mon, 18 Apr 2005 20:36:05 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 242525CDC; Mon, 18 Apr 2005 16:36:05 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57620-06; Mon, 18 Apr 2005 16:36:04 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-53-96.ny325.east.verizon.net [68.161.53.96]) by pi.codefab.com (Postfix) with ESMTP id 32EA35C1E; Mon, 18 Apr 2005 16:36:03 -0400 (EDT) Message-ID: <42641A21.5080208@mac.com> Date: Mon, 18 Apr 2005 16:35:45 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joel References: <200504170655.27864.krinklyfig@spymac.com> <20050417225347.GA9600@gurney.reilly.home> <20050418103032.9618.REES@ddcom.co.jp> In-Reply-To: <20050418103032.9618.REES@ddcom.co.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com cc: freebsd-stable@freebsd.org Subject: Re: 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: Mon, 18 Apr 2005 20:36:06 -0000 Joel wrote: [ ... ] > Maybe it's because I'm such a newb, but I'm wondering which program has > what bug? Is it that the default configuration files for the login logs > doesn't put on age limit on the rotation? Is it that the log lines don't > conain a full 4-digit year in the timestamp? This last one is correct: the standard syslog format doesn't include a 4-digit year value in the timestamp. All sorts of nasty logfile rolling and parsing issues would be made much easier to do right if it did... -- -Chuck