Anthony J. Bentley wrote:
David Uhden Collado writes:
It also documents the complete procedure:
- adding the login class;
- rebuilding login.conf.db with cap_mkdb(8);
...
+Rebuild the login class database so the change takes effect:
+
+ # cap_mkdb /etc/login.conf
Please do not suggest cap_mkdb. It's not necessary to make the changes
take effect and is more problematic than helpful.
It may not actually be necessary, and it could even introduce problems
because the database is not automatically kept in sync with the login
class configuration file. What I do not understand, then, is why the
system allows you to build a database for login classes in the first
place. If the database is not intended to be the authoritative
representation of login.conf, what is the actual purpose of that feature?
