bin/41660: updates to /etc/login.conf and running cap_mkdb does not affect the system

[kordex%gmail.com@localhost]

>Number:         41660
>Category:       bin
>Synopsis:       updates to /etc/login.conf and running cap_mkdb does not 
>affect the system
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 01 17:35:00 +0000 2009
>Originator:     Mikko Kortelainen
>Release:        NetBSD 5.0
>Organization:
-
>Environment:
NetBSD lanex 5.0 NetBSD 5.0 (GENERIC) #0: Sun Apr 26 18:50:08 UTC 2009  
builds%b6.netbsd.org@localhost:/home/builds/ab/netbsd-5-0-RELEASE/i386/200904260229Z-obj/home/builds/ab/netbsd-5-0-RELEASE/src/sys/arch/i386/compile/GENERIC
 i386

>Description:
updating changes to /etc/login.conf and running cap_mkdb does not cause 
login(1) to have altered configuration. only removing /etc/login.conf.db did 
cause the use of altered configuration.
>How-To-Repeat:
edit /etc/login.conf to your likings (mine):

default:\
        :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R7/bin /usr/X11R6/bin 
/usr/pkg/bin /usr/pkg/sbin /usr/local/bin:\
        :umask=022:\
        :datasize-max=2048M:\
        :datasize-cur=1024M:\
        :maxproc-max=1024:\
        :maxproc-cur=512:\
        :openfiles-cur=1024:\
        :stacksize-cur=8M:

run cap_mkdb /etc/login.conf

relogin
check with ulimit -a
no changes applied.
>Fix:
rm /etc/login.conf.db ; cap_mkdb /etc/login.conf