Table of Contents
Advertisement
Choose whether to load the password database at startup.
6.
For more information, see "Loading the Entire Password File on Startup," on
page 359.
Choose whether to apply a configuration style.
7.
Click OK.
8.
For more information, see the online help for the User Document Directories page.
Another way to give users separate directories is to create a URL mapping to a
central directory that all of your users can modify.
Restricting Content Publication
In some situations a system administrator may want to restrict what user accounts
are able to publish content via user document directories. To restrict a user's
publishing, add a trailing slash to the user's home directory path in the
:
/etc/passwd file
jdoe::1234:1234:John Doe:/home/jdoe:/bin/sh
becomes:
jdoe::1234:1234:John Doe:/home/jdoe/:/bin/sh
After you make this modification, Netscape Enterprise Server will not serve pages
from this user's directory. The browser requesting the URI receives a "404 File Not
Found" error and a 404 error will be logged to the Enterprise Server access log. No
error will be logged to the errors log.
If, at a later time, you decide to allow this user to publish content, remove the
trailing slash from the
Loading the Entire Password File on Startup
You also have the option of loading the entire password file on startup. If you
choose this option, the server loads the password file into memory when it starts,
making user lookups much faster. If you have a very large password file, however,
this option can use too much memory.
Customizing User Public Information Directories (Unix/Linux)
entry, then restart Enterprise Server.
/etc/passwd
Chapter 16
Content Management
359
Advertisement
Table of Contents
