From owner-freebsd-stable@FreeBSD.ORG Tue Apr 15 11:43:01 2003 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 DBB8537B401 for ; Tue, 15 Apr 2003 11:43:01 -0700 (PDT) Received: from mail.urchin.com (ns2.quantified.com [63.212.171.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4153043F93 for ; Tue, 15 Apr 2003 11:43:01 -0700 (PDT) (envelope-from dsilver@urchin.com) Received: from support.urchin.com (support.urchin.com [63.212.171.7]) by mail.urchin.com (8.12.9/8.12.1) with ESMTP id h3FIhIuf048576; Tue, 15 Apr 2003 11:42:57 -0701 (PDT) (envelope-from dsilver@urchin.com) Received: from danzig.sd.quantified.net (web.urchin.com [63.212.171.5]) (authenticated bits=0) by support.urchin.com (8.12.8/8.12.6) with ESMTP id h3FIgxsL076112; Tue, 15 Apr 2003 11:43:00 -0700 (PDT) (envelope-from dsilver@urchin.com) From: Doug Silver Organization: Urchin Software Corporation To: Kent Stewart , stable@freebsd.org Date: Tue, 15 Apr 2003 11:43:27 -0700 User-Agent: KMail/1.5.1 References: <200304151126.21202.dsilver@urchin.com> <200304151132.51599.kstewart@owt.com> In-Reply-To: <200304151132.51599.kstewart@owt.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304151143.05916.dsilver@urchin.com> X-Filter-Version: 1.7 (mail.urchin.com) Subject: Re: Problem logging in after upgrade to 4.8-Stable 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: Tue, 15 Apr 2003 18:43:02 -0000 On Tuesday 15 April 2003 11:32 am, Kent Stewart wrote: > On Tuesday 15 April 2003 11:26 am, Doug Silver wrote: > > I upgraded two 4.7 machines yesterday to 4.8-stable and now normal > > users can't login (both at the console and ssh). Root logs in okay. > > I created a new user and that works. However, the first server I > > upgraded to 4.8 hasn't had the same problems. I changed my personal > > password as root on one of the problem servers and then I was able to > > login. Did something change in the password algorithm to cause this > > to happen or is it something else? > > > > Any suggestions?? > > Can not say for sure but this usually happens when you don't pay > attention during mergemaster. If you let it update master.passwd, you > end up with a clean system and lose your users. > > Lemt I agree. Mergemaster did not remove the users, they are still in there. I even ran "/usr/sbin/pwd_mkdb -p /etc/master.passwd" just to see if that would solve it, but no luck. It seems very odd that root could login fine, but I couldn't, and then a new user could. -doug