Add a note to inform users that they need to build login.conf.db from
login.conf in place of just recommending they read the manual page. Submitted by: Bill Moran <wmoran@potentialtech.com>
This commit is contained in:
parent
1a4f679ada
commit
283044d2c5
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=21775
1 changed files with 11 additions and 0 deletions
|
@ -782,6 +782,17 @@ passwd: done</screen>
|
|||
string processed accordingly depending on the name. Setting up login
|
||||
classes and capabilities is rather straight-forward and is also
|
||||
described in &man.login.conf.5;.</para>
|
||||
|
||||
<note>
|
||||
<para>The system does not read the configuration in
|
||||
<filename>/etc/login.conf</filename> directly, but reads the database
|
||||
file <filename>/etc/login.conf.db</filename>.
|
||||
To generate <filename>/etc/login.conf.db</filename> from
|
||||
<filename>/etc/login.conf</filename>, execute the following
|
||||
command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cap_mkdb -f /etc/login.conf /etc/login.conf</userinput></screen>
|
||||
</note>
|
||||
|
||||
<para>Resource limits are different from plain vanilla login
|
||||
capabilities in two ways. First, for every limit, there is a soft
|
||||
|
|
Loading…
Reference in a new issue