Bug 241412 - Discrepancy between login.conf(5) and handbook w.r.t. cases when cap_mkdb(1) usage is necessary.
Summary: Discrepancy between login.conf(5) and handbook w.r.t. cases when cap_mkdb(1) ...
Status: New
Alias: None
Product: Documentation
Classification: Unclassified
Component: Documentation (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-doc mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-22 11:19 UTC by alexandrian.librarian1
Modified: 2019-10-22 11:19 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alexandrian.librarian1 2019-10-22 11:19:53 UTC
In the handbook's (https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/using-localization.html#locale-lang-country) section 22.2.1.1. Login Classes Method, we have:

   Whenever /etc/login.conf is edited, remember to execute the following command to update the capability database:

	 # cap_mkdb /etc/login.conf

But in login.conf(5) for FreeBSD 12X we have:

    The default /etc/login.conf shipped with FreeBSD is an out	of the box
     configuration.  Whenever changes to this, or the user's ~/.login_conf,
     file are made, the	modifications will not be picked up until cap_mkdb(1)
     is	used to	compile	the file into a	database.

The wording in the handbook can be easily interpreted to imply that cap_mkdb(1) need only be used when /etc/.login_conf is modified. But this is not the case - as can be seen from login.conf(5). I request that the handbook includes that cap_mkdb(1) needs to be used even when ~/.login_conf is modified.