Subject: login.conf - default class
To: None <>
From: rudolf <>
List: tech-userlevel
Date: 08/22/2005 22:04:55

I was trying to employ login.conf to raise limits for one login class 
while I didn't add a 'default' entry to login.conf file. The consequence 
was that I wasn't able to login as (or su to) root anymore. The system 
is NetBSD-3_BETA. This popped up on the console: 'pam_acct_mgmt: error 
in service module' during the root's unsuccessful login. I fixed it from 
the single-user adding just 'default:' line to login.conf.

So I would like to ask: is this the intended behaviour? Shouldn't be the 
login.conf man page a little more verbose about missing default entry? 
(I was not expecting that my intervention will break the system, 
reasoning from this line: "A special class called ``default'' will be 
used (if it exists) if there is no other match.")

Maybe we can have a login.conf file in /etc/defaults including just 
'defaults:' ?