From owner-freebsd-hackers  Thu Mar  6 00:22:06 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA03625
          for hackers-outgoing; Thu, 6 Mar 1997 00:22:06 -0800 (PST)
Received: from shadows.aeon.net (bsdhack@shadows.aeon.net [194.100.41.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA03620
          for <freebsd-hackers@freebsd.org>; Thu, 6 Mar 1997 00:22:01 -0800 (PST)
Received: (from bsdhack@localhost)
          by shadows.aeon.net (8.8.5/8.8.3) id KAA20723;
          Thu, 6 Mar 1997 10:20:02 +0200 (EET)
From: mika ruohotie <bsdhack@shadows.aeon.net>
Message-Id: <199703060820.KAA20723@shadows.aeon.net>
Subject: Re: strange syslog messagey
In-Reply-To: <199703041041.FAA02357@yakko.my.domain> from Lee Cremeans at "Mar 4, 97 05:41:56 am"
To: mcampbel@erols.com
Date: Thu, 6 Mar 1997 10:20:02 +0200 (EET)
Cc: freebsd-hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > > Mar  3 13:39:40 trinity syslog: /etc/pwd.db: Invalid argument
> > my 2.1.7 does this too, no chroots...
> I ran into this myself one day; don't exactly remember the circumstances,
> but recompiling my pwd.db made it go away.

ditto. firing up vipw and making it to remake db wipes it away, and i
assume it was netscape communicator beta2 that did it atleast few times...


mickey