From owner-freebsd-isp Wed Jul 19 19:32:32 2000 Delivered-To: freebsd-isp@freebsd.org Received: from ns.tcworks.net (ns.tcworks.net [216.61.218.2]) by hub.freebsd.org (Postfix) with ESMTP id BC73D37B9E6 for ; Wed, 19 Jul 2000 19:32:28 -0700 (PDT) (envelope-from ccook@tcworks.net) Received: from tcworks.net (stuck.sticky.org [216.61.218.6]) by ns.tcworks.net (8.9.2/8.9.2) with ESMTP id VAA41247; Wed, 19 Jul 2000 21:27:58 -0500 (CDT) (envelope-from ccook@tcworks.net) Message-ID: <39761E78.5A3E1CFD@tcworks.net> Date: Wed, 19 Jul 2000 21:32:40 +0000 From: Chris Cook X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isp@FreeBSD.ORG Cc: simon@optinet.com Subject: Re: HELP! Cannot read passwd file References: <3975E544.637A5FB6@tcworks.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org OK, I've fixed this problem... appears that somehow /etc/group went /dev/null in between some password changes and blitzed out the system. Apparently because of that it corrupted master.passwd which needed a pwd_mkdb to repair, I pulled a /etc/group from /var/backups and everything seems fixed... thanks! Chris Cook wrote to freebsd-isp@freebsd.org: > > Hey there, > One of our boxes boots up but acts like it cannot read the passwd or > group file. It seems that maybe somehow the encryption type has changed > and it is not using DES anymore? How can I make sure it is using the > proper encryption? It is running 3.1-RELEASE and when it boots up I > cannot login and it gives errors saying "user unknown" and group unknown > when loading stuff in rc.local ... please help. TIA -- Chris o----< ccook@tcworks.net >-----------------------------------------o |Chris Cook - Network Admin | TCWORKS.NET - http://www.tcworks.net | |The Computer Works ISP | FreeBSD - http://www.freebsd.org | o------------------------------------------------------------------o To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message