Date: Tue, 22 Oct 2019 11:19:53 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 241412] Discrepancy between login.conf(5) and handbook w.r.t. cases when cap_mkdb(1) usage is necessary. Message-ID: <bug-241412-9@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241412 Bug ID: 241412 Summary: Discrepancy between login.conf(5) and handbook w.r.t. cases when cap_mkdb(1) usage is necessary. Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Documentation Assignee: doc@FreeBSD.org Reporter: alexandrian.librarian1@gmail.com 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. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241412-9>