# cd /etc/yum.repos.d 
# wget http://directory.fedoraproject.org/sources/idmcommon.repo 
# wget http://directory.fedoraproject.org/sources/dirsrv.repo 

# yum install svrcore mozldap perl-Mozilla-LDAP libicu
# rpm --import http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/RPM-GPG-KEY-fedora 
# rpm --import http://download.fedora.redhat.com/pub/fedora/linux/extras/RPM-GPG-KEY-Fedora-Extras
# rpm -ivh http://download.fedora.redhat.com/pub/fedora/linux/extras/6/i386/adminutil-1.1.5-1.fc6.i386.rpm
# rpm -ivh http://download.fedora.redhat.com/pub/fedora/linux/extras/6/i386/jss-4.2.5-1.fc6.i386.rpm

# yum install fedora-ds

# cp -a /etc/dirsrv /etc/dirsrv.orig

# setup-ds-admin.pl

==============================================================================
Your system has been scanned for potential problems, missing patches, 
etc.  The following output is a report of the items found that need to 
be addressed before running this software in a production 
environment. 

Fedora Directory Server system tuning analysis version 10-AUGUST-2007. 

NOTICE : System is i686-unknown-linux2.6.18-53.1.21.el5 (1 processor). 

ERROR  : Only 122MB of physical memory is available on the system. 256MB is the 
recommended minimum. 1024MB is recommended for best performance on large production system. 

NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds 
(120 minutes).  This may cause temporary server congestion from lost 
client connections. 

WARNING: There are only 1024 file descriptors (hard limit) available, which 
limit the number of simultaneous connections.  

WARNING: There are only 1024 file descriptors (soft limit) available, which 
limit the number of simultaneous connections.  

ERROR  : The above errors MUST be corrected before proceeding. 

Would you like to continue? [no]: yes 

==============================================================================
Choose a setup type: 

   1. Express 
       Allows you to quickly set up the servers using the most 
       common options and pre-defined defaults. Useful for quick 
       evaluation of the products. 

   2. Typical 
       Allows you to specify common defaults and options. 

   3. Custom 
       Allows you to specify more advanced options. This is 
       recommended for experienced server administrators only. 

To accept the default shown in brackets, press the Enter key. 

Choose a setup type [2]: 

==============================================================================
Enter the fully qualified domain name of the computer 
on which you're setting up server software. Using the form 
. 
Example: eros.example.com. 

To accept the default shown in brackets, press the Enter key. 

Computer name [cos5a.bluecoara.net]: 

==============================================================================
The servers must run as a specific user in a specific group. 
It is strongly recommended that this user should have no privileges 
on the computer (i.e. a non-root user).  The setup procedure 
will give this user/group some permissions in specific paths/files 
to perform server-specific operations. 

If you have not yet created a user and group for the servers, 
create this user and group using your native operating 
system utilities. 

System User [nobody]: 
System Group [nobody]: 

==============================================================================
Server information is stored in the configuration directory server. 
This information is used by the console and administration server to 
configure and manage your servers.  If you have already set up a 
configuration directory server, you should register any servers you 
set up or create with the configuration server.  To do so, the 
following information about the configuration server is required: the 
fully qualified host name of the form 
.(e.g. hostname.example.com), the port number 
(default 389), the suffix, the DN and password of a user having 
permission to write the configuration information, usually the 
configuration directory administrator, and if you are using security 
(TLS/SSL).  If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port 
number (default 636) instead of the regular LDAP port number, and 
provide the CA certificate (in PEM/ASCII format). 

If you do not yet have a configuration directory server, enter 'No' to 
be prompted to set up one. 

Do you want to register this software with an existing 
configuration directory server? [no]: 

==============================================================================
Please enter the administrator ID for the configuration directory 
server.  This is the ID typically used to log in to the console.  You 
will also be prompted for the password. 

Configuration directory server 
administrator ID [admin]: 
Password: 
Password (confirm): 

============================================================================== 
The information stored in the configuration directory server can be 
separated into different Administration Domains.  If you are managing 
multiple software releases at the same time, or managing information 
about multiple domains, you may use the Administration Domain to keep 
them separate. 

If you are not using administrative domains, press Enter to select the 
default.  Otherwise, enter some descriptive, unique name for the 
administration domain, such as the name of the organization 
responsible for managing the domain. 

Administration Domain [bluecoara.net]: 

============================================================================== 
The standard directory server network port number is 389.  However, if 
you are not logged as the superuser, or port 389 is in use, the 
default value will be a random unused port number greater than 1024. 
If you want to use port 389, make sure that you are logged in as the 
superuser, that port 389 is not in use. 

Directory server network port [389]: 

============================================================================== 
Each instance of a directory server requires a unique identifier. 
This identifier is used to name the various 
instance specific files and directories in the file system, 
as well as for other uses as a server instance identifier. 

Directory server identifier [cos5a]: 

============================================================================== 
The suffix is the root of your directory tree.  The suffix must be a valid DN. 
It is recommended that you use the dc=domaincomponent suffix convention. 
For example, if your domain is example.com, 
you should use dc=example,dc=com for your suffix. 
Setup will create this initial suffix for you, 
but you may have more than one suffix. 
Use the directory server utilities to create additional suffixes. 

Suffix [dc=bluecoara, dc=net]: 

============================================================================== 
Certain directory server operations require an administrative user. 
This user is referred to as the Directory Manager and typically has a 
bind Distinguished Name (DN) of cn=Directory Manager. 
You will also be prompted for the password for this user.  The password must 
be at least 8 characters long, and contain no spaces. 

Directory Manager DN [cn=Directory Manager]: 
Password: 
Password (confirm): 

============================================================================== 
The Administration Server is separate from any of your web or application 
servers since it listens to a different port and access to it is 
restricted. 

Pick a port number between 1024 and 65535 to run your Administration 
Server on. You should NOT use a port number which you plan to 
run a web or application server on, rather, select a number which you 
will remember and which will not be used for anything else. 

Administration port [9830]: 

============================================================================== 
The interactive phase is complete.  The script will now set up your 
servers.  Enter No or go Back if you want to change something. 

Are you ready to set up your servers? [yes]: 
Creating directory server . . . 
Your new DS instance 'cos5a' was successfully created. 
Creating the configuration directory server . . . 
Beginning Admin Server creation . . . 
Creating Admin Server files and directories . . . 
Updating adm.conf . . . 
Updating admpw . . . 
Registering admin server with the configuration directory server . . . 
Updating adm.conf with information from configuration directory server . . . 
Updating the configuration for the httpd engine . . . 
Starting admin server . . . 
output: httpd.worker: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName 
The admin server was successfully started. 
Admin server was successfully created, configured, and started. 
Exiting . . . 
Log file is '/tmp/setupdqCaHW.log'