From owner-freebsd-hackers Sat Jan 30 11:19:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27650 for freebsd-hackers-outgoing; Sat, 30 Jan 1999 11:19:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zoe.iserve.net (zoe.iserve.net [207.250.219.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27645 for ; Sat, 30 Jan 1999 11:19:20 -0800 (PST) (envelope-from rch@iserve.net) Received: from acidic (acidic.iserve.net [207.250.219.40]) by zoe.iserve.net (8.9.1/8.9.1) with SMTP id OAA00767 for ; Sat, 30 Jan 1999 14:18:48 -0500 (EST) Message-Id: <199901301918.OAA00767@zoe.iserve.net> X-Sender: rch@iserve.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Sat, 30 Jan 1999 14:20:00 -0500 To: freebsd-hackers@FreeBSD.ORG From: Robert Hough Subject: pwd.db corruption Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running a machine with FreeBSD 2.2.2-RELEASE and about 4 times now, the pwd.db file has become corrupt. When this happens, it wont authenticate anyone, and I have to reboot into single user mode, remove the pwd.db (rename it to pwd.old basically), and add a new user. After a reboot, it is fine, untill it happens again. Can someone give me some pointers on how to correct this problem? Is it a known bug in 2.2.2? I've already decided to upgrade the machine to later build, but that will be on a completely new machine, untill then I'd like to at least make sure this doesn't pop up on me again, or worse, when I'm not around to fix it. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message