From nobody@FreeBSD.org  Tue Dec 14 20:19:13 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D9D5F16A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 14 Dec 2004 20:19:13 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B6BB943D49
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 14 Dec 2004 20:19:13 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id iBEKJDsh012264
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 14 Dec 2004 20:19:13 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id iBEKJDu8012217;
	Tue, 14 Dec 2004 20:19:13 GMT
	(envelope-from nobody)
Message-Id: <200412142019.iBEKJDu8012217@www.freebsd.org>
Date: Tue, 14 Dec 2004 20:19:13 GMT
From: Rostislav Krasny <rosti_bsd@yahoo.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: login.conf(5) manual page says nothing about a hashed form of the login capabilities database and its use
X-Send-Pr-Version: www-2.3
X-GNATS-Notify: trhodes

>Number:         75068
>Category:       docs
>Synopsis:       login.conf(5) manual page says nothing about a hashed form of the login capabilities database and its use
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 14 20:20:31 GMT 2004
>Closed-Date:    Thu Oct 12 19:28:39 GMT 2006
>Last-Modified:  Thu Oct 12 19:28:39 GMT 2006
>Originator:     Rostislav Krasny
>Release:        5.3-RELEASE
>Organization:
>Environment:
FreeBSD saturn 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Fri Dec  3 13:57:01 IST 2004     root@saturn:/usr/obj/usr/src/sys/MYKERNEL  i386
>Description:
login.conf(5) manual page says nothing about a hashed form of the login capabilities database and its use. One might not get to know from the manual that if his system have an /etc/login.conf.db file then he must run 'cap_mkdb /etc/login.conf' after each change of /etc/login.conf because login.conf.db have a higher preference over login.conf; and if there is only /etc/login.conf then hi shouldn't run that command.
>How-To-Repeat:
man 5 login.conf
>Fix:
FreeBSD 4.8 Errata have following text:

FreeBSD supports a hashed form of the login capabilities database, stored in /etc/login.conf.db. This is generated from the /etc/login.conf text file. If the hashed database is present, login(1) will use it in preference to the contents of the text file. FreeBSD 4.8-RELEASE is the first release that actually includes /etc/login.conf.db on the distribution media; thus, users modifying /etc/login.conf need to remember to regenerate the database, using cap_mkdb(1). Users performing source upgrades are generally not affected by this change, because mergemaster(8) offers the option to regenerate /etc/login.conf.db during upgrades. login.conf(5) has more details on the format and usage of the login capabilities database.

I think something like that should be added to the login.conf(5) manual page and '/etc/login.conf.db' to the manual's synopsis.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: ru 
State-Changed-When: Thu Oct 12 19:28:01 UTC 2006 
State-Changed-Why:  
Superseded by PR docs/76981. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=75068 
>Unformatted:
