
Option
Overview of Setup
|
|
|
|
|
|
|
|
|
Alternate Options |
|
| Description |
|
| Example |
|
|
|
|
| specifies a log file to |
|
|
| ||
|
|
| which to write the |
|
|
| ||
|
|
|
|
| /export/example2007.log |
| ||
|
|
| output. If this is not |
|
|
| ||
|
|
|
|
|
|
|
| |
|
|
| set, then the setup |
|
| For no log file, set the |
| |
|
|
| information is written |
|
|
| ||
|
|
|
|
| file name to |
| ||
|
|
| to a temporary file. |
|
|
| ||
|
|
|
|
| /dev/null: |
| ||
|
|
|
|
|
|
| ||
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
|
Table 1.1. setup-ds-admin Options
4. Overview of Setup
After the Directory Server packages are installed, there is a script,
•Express — The fastest setup mode. This requires minimal interaction and uses default values for almost all settings. Because express installation does not offer the choice of selecting the Directory Server server port number or the directory suffix, among other settings, Red Hat recommends that you not use it for production deployments. Also, express setups can fail if default configuration values are not available because there is no way to offer an alternative.
•Typical — The default and most common setup mode. This prompts you to supply more detailed information about the directory service, like suffix and configuration directory information, while still proceeding quickly through the setup process.
•Custom — The most detailed setup mode. This provides more control over Administration Server settings and also allows data to be imported into the Directory Server at setup, so that entries are already populated in the databases when the setup is complete.
The information requested with the setup process is described in Table 1.2, “Comparison of Setup Types”.
There is a fourth setup option, silent setup, which uses a configuration file and
9