Red Hat NETSCAPE DIRECTORY SERVER 7.0 - DEPLOYMENT Installation Guide download pdf (Page 42)

WARNING

If Directory Server is already installed on your machine, it is extremely important that you perform

a migration, not a fresh installation. Migration is described in Chapter 5, Migrating from Previous

Versions.

1. After the Directory Server packages are installed as described in Section 3.1, “Installing the

Directory Server Packages”, then launch the setup-ds-adm in.pl script.

# /usr/sbin/setup-ds-adm in.pl

This script allows parameters to be passed with it or to specify configuration files to use. The

options are described more in Section 1.3, “About the setup-ds-admin.pl Script”.

2. Select y to accept the Red Hat licensing terms.

3. The dsktune utility runs. Select y to continue with the setup.

dsktune checks the available disk space, processor type, physical memory, and other system

data and settings such as T CP/IP ports and file descriptor settings. If your system does not meet

these basic Red Hat Directory Server requirements, dsktune returns a warning. dsktune

warnings do not block the setup process; simply entree y to go to the next step.

4. Next, choose the setup type. Accept the default, option 3, to perform a custom setup.

5. Set the computer name of the machine on which the Directory Server is being configured. This

defaults to the fully-qualified domain name (FQDN) for the host. For example:

Computer name [ldap.example.com]:

The given hostname must be a fully-qualified domain name that can be resolved using

gethostname() and then can be reverse-resolved by IP address (IPv4 or IPv6) back to the

original hostname. If either name resolution attempt fails, then the setup script returns a warning

message and prompts you to continue.

NOTE

The Directory Server requires the fully-qualified domain name to set up the servers, as

described in Section 1.2.1, “Resolving the Fully-qualified Domain Name”. T he setup script

uses the system's gethostname() function to obtain the hostname (such as ldap) and

the /etc/resolv.conf file to identify the domain name (such as example.com ).

Therefore, if there are aliases in the /etc/hosts file that do not match the specified

domains in the /etc/resolv.conf settings, the setup script cannot correctly generate

the fully-qualified domain name as it is used by DNS, and the default options in the prompts

are wrong.

The hostname is very important. It is used generate the Directory Server instance name, the

admin domain, and the base suffix, among others. If you are using SSL/T LS or Kerberos, the

computer name must be the exact name that clients use to connect to the system. If you will use

DNS, make sure the name resolves to a valid IP address (IPv4 or IPv6) and that IP address

resolves back to this name.

6. Set the user and group as which the Directory Server process will run. T he default is

nobody:nobody. For example:

Chapter 3. Setting up Red Hat D irectory Server on Red Hat Enterprise Linux

1 2 ... 37 38 39 40 41 42 43 44 45 46 47 ... 114 115

No comments

Red Hat NETSCAPE DIRECTORY SERVER 7.0 - DEPLOYMENT Installation Guide Page 42