From owner-freebsd-current  Tue Feb 19 10:33:29 2002
Delivered-To: freebsd-current@freebsd.org
Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15])
	by hub.freebsd.org (Postfix) with ESMTP
	id CA3B337B404; Tue, 19 Feb 2002 10:33:16 -0800 (PST)
Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5])
	by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id UAA13395;
	Tue, 19 Feb 2002 20:33:14 +0200 (EET)
	(envelope-from sobomax@FreeBSD.org)
Received: from vega.vega.com (h21.229.dialup.iptcom.net [212.9.229.21])
	by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id UAA45991;
	Tue, 19 Feb 2002 20:33:13 +0200 (EET)
	(envelope-from sobomax@FreeBSD.org)
Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1])
	by vega.vega.com (8.11.6/8.11.3) with ESMTP id g1JIFKd88210;
	Tue, 19 Feb 2002 20:15:20 +0200 (EET)
	(envelope-from sobomax@FreeBSD.org)
Message-ID: <3C729655.27B995F2@FreeBSD.org>
Date: Tue, 19 Feb 2002 20:15:49 +0200
From: Maxim Sobolev <sobomax@FreeBSD.org>
Organization: Vega International Capital
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,uk,ru
MIME-Version: 1.0
To: des@FreeBSD.org, current@FreeBSD.org
Subject: Re: Either PAM or login is broken
References: <3C72944A.8C6EDF79@FreeBSD.org>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Ok, I've found the problem - it appears that my machine didn't have a
/var/log/lastlog file and so far pam_lastlog.so was quite happy with
this situation, while after a make world it doesn't tolerate it
anymore. I am not sure that such POLA change is good and IMO
pam_lastlog.so shouldn't refuse login just because there is no
/var/log/lastlog file or at least it should create the file by itself.

Please fix.

-Maxim

Maxim Sobolev wrote:
> 
> Hi,
> 
> Just upgraded by -current box and after a reboot found that I'm no
> longer able to log-in neither from console, nor from the network.
> Following is the log:
> 
> FreeBSD/i386 (notebook) (ttyv0)
> 
> login: root
> Password:
> Feb 19 19:59:35 notebook login: pan_open_session(): Error in service
> module
> 
> FreeBSD/i386 (notebook) (ttyv0)
> 
> login:
> 
> I have no idea what does it mean - I performed full make world, make
> kernel and did a /etc update using mergemaster.
> 
> Please fix.
> 
> -Maxim
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message