From owner-freebsd-questions@FreeBSD.ORG Tue May 25 11:36:14 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 909BA16A4CE for ; Tue, 25 May 2004 11:36:14 -0700 (PDT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23BEF43D2D for ; Tue, 25 May 2004 11:36:14 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (sccrmhc12) with ESMTP id <20040525183543012007hojie>; Tue, 25 May 2004 18:35:53 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id E1A5D82; Tue, 25 May 2004 14:35:42 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Uwe Doering References: <200405250742.i4P7gDp22491@server1.web-mania.com> <40B3056C.8070803@geminix.org> From: Lowell Gilbert Date: 25 May 2004 14:35:42 -0400 In-Reply-To: <40B3056C.8070803@geminix.org> Message-ID: <44brkcbbi9.fsf@be-well.ilk.org> Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: Security run question 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, 25 May 2004 18:36:14 -0000 Uwe Doering writes: > Edd wrote: > > I recieved my security run today (as usual) and an error which I have > > never seen before appeared: > > hitbox.monsternet.lan kernel log messages: > > > >>tabase /etc/aliases.db: No such file or directory > > A quick locate shows that there is no such command as tabase! Any > > ideas > > what this might be? > > That should probably read "database", and the message just got clipped > for some reason. Some program apparently tried to access > '/etc/aliases.db', failed to do so and logged an error message, which > the security run scripts subsequently reported to you. No, it's more benign than that. What almost certainly happened is that the first part of a line from the *top* of the dmesg buffer got clipped off, and so this is only the *end* of an *old* log message.