Subject: Re: bin/32903: utmp remains empty
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,>
From: Christos Zoulas <christos@zoulas.com>
List: netbsd-bugs
Date: 03/13/2006 00:25:02
The following reply was made to PR bin/32903; it has been noted by GNATS.

From: christos@zoulas.com (Christos Zoulas)
To: gnats-bugs@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org, i18rabbit@cwazy.co.uk
Cc: 
Subject: Re: bin/32903: utmp remains empty
Date: Sun, 12 Mar 2006 19:24:51 -0500

 On Mar 13, 12:15am, i18rabbit@cwazy.co.uk (i18rabbit@cwazy.co.uk) wrote:
 -- Subject: Re: bin/32903: utmp remains empty
 
 |  >  Do you have /etc/pam.d?
 |  
 |  no, i have a /etc/pam.conf.  but i don't see how that is relevant.
 |  i can run login manually - and according to the login(1) manpage,
 |  that should be sufficient to make utmp entries.
 
 The man page does not specify what mechanism is used to write the
 utmp/utmpx pages. Under pam this mechanism is pam_lastlog.
 
 |  # service + type        control     module          arguments
 |  # ######### ########### ########### ############### ###############
 |  # prog name account     requisite   : failure = auth termination.
 |  #    or     auth        required    : failure = try next auth, if any.
 |  #  "other"  password    sufficient  : success = OK, unless previous failed.
 |  # (default) session     optional    : success only important if last auth.
 |  # ######### ########### ########### ############### ############### 
 |  
 |  other       account     required    pam_unix.so     try_first_pass
 |  other       auth        required    pam_unix.so     try_first_pass
 |  other       password    required    pam_unix.so     try_first_pass
 |  other       session     required    pam_permit.so
 
 - You report problems.
 - We ask you if you've changed anything.
 - You say it used to work in 2.0 and you did not change anything since then.
 - We mention pam.d.
 - You get upset because we are not helpful solving your problem.
 - You reveal that you use your own home-brewed pam.conf that is missing
   a lot of other configuration (for example pam_nologin, pam_securetty,
   pam_login_access, pam_self) that will make other things break.
 
 Am I missing something?
 
 christos