From owner-freebsd-current@FreeBSD.ORG Sun May 15 21:20:24 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E5F416A4CE for ; Sun, 15 May 2005 21:20:24 +0000 (GMT) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id C420143DD8 for ; Sun, 15 May 2005 21:20:23 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from Sonomago (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 3DB0219F3B; Sun, 15 May 2005 14:21:01 -0700 (PDT) From: "Darren Pilgrim" To: =?iso-8859-1?Q?'=22Dag-Erling_Sm=F8rgrav=22'?= Date: Sun, 15 May 2005 14:20:11 -0700 Message-ID: <000a01c55993$e4b6d8a0$0a2a15ac@Sonomago> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Importance: Normal In-Reply-To: <86br7dewqh.fsf@xps.des.no> cc: freebsd-current@freebsd.org Subject: RE: cannot log on as root after upgrade X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 May 2005 21:20:24 -0000 From: "Dag-Erling Sm=F8rgrav" [mailto:des@des.no]=20 > "Darren Pilgrim" writes: >> >> [Paraphrased] Logging in on the console as root produces >> "pam_acct_mgmt(): authentication error" message and login failure. >=20 > This is not a PAM bug. Someone broke ttyname() so the code that > checks if you are logging in on a secure tty fails. Quick workaround: > comment out the pam_securetty line in /etc/pam.d/login. The workaround has made direct root logins possible again, thanks. I've just now noticed another error message--this one upon log-out. I = don't have the exact text of the error message (I couldn't find it in the log files), but the text is like "no utmp entry for tty??" or "could not = remove utmp entry for tty??" with the question marks actually there, instead of = the real name of the tty I was logged in on. Is this error message also due = to the breakage?