From owner-freebsd-current Thu Mar 7 8: 1: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id BEB2D37B405; Thu, 7 Mar 2002 08:00:59 -0800 (PST) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.11.6/8.11.6) with UUCP id g27G0wP56198; Thu, 7 Mar 2002 16:00:58 GMT (envelope-from mark@grimreaper.grondar.za) Received: from grimreaper (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.2/8.12.2) with ESMTP id g27FuhRV022171; Thu, 7 Mar 2002 15:56:43 GMT (envelope-from mark@grimreaper.grondar.za) Message-Id: <200203071556.g27FuhRV022171@grimreaper.grondar.org> To: Rasmus Skaarup Cc: des@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 5-CURRENT source upgrade path is broken in PAM References: <20020307164346.F46540-100000@skaarup.org> In-Reply-To: <20020307164346.F46540-100000@skaarup.org> ; from Rasmus Skaarup "Thu, 07 Mar 2002 16:45:59 +0100." Date: Thu, 07 Mar 2002 15:56:43 +0000 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I can't login as root either, I can only gain root access if I boot into > single-user. > > The login process just eats up all cpu-ressources and the login times out > after 300 seconds. A su doesn't work either, of course. Not a PAM problem, a crypt(3) problem. My fault, and fixed. M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message