Attachment 162025 Details for Bug 253811 – sample usage

sample usage

reg.txt (text/plain), 6.28 KB, created by Noriko Hosoi on 2007-08-22 02:27:49 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Noriko Hosoi

Created: 2007-08-22 02:27:49 UTC

Size: 6.28 KB

patch

obsolete

>[Sample usage]
>Setup 3 LDAP servers:
>  ./etc/dirsrv/slapd-laputa/dse.ldif
>  ./tmp/slapd-laputa3/dse.ldif
>  ./slapd-laputa2/dse.ldif
>
>$ sbin/register-ds-admin.pl
>Beginning registration of the Directory Server
>==============================================================================
>The Directory Server locates its configuration file (dse.ldif) at /export/servers/ds72/etc/dirsrv/slapd-ID, by default.  If you have Directory Server(s) which configuration file is put at the other location, you need to input it to register the server.
>
>If you have such Directory Server, type the full path that stores the configuration file.
>
>If you don't, type return.
>[configuration directory path or return]: /export/servers/ds72
>
>
>==============================================================================
>The Directory Server locates its configuration file (dse.ldif) at /export/servers/ds72/etc/dirsrv/slapd-ID, by default.  If you have Directory Server(s) which configuration file is put at the other location, you need to input it to register the server.
>
>If you have such Directory Server, type the full path that stores the configuration file.
>
>If you don't, type return.
>[configuration directory path or return]: /export/servers/ds72/tmp
>
>
>==============================================================================
>The Directory Server locates its configuration file (dse.ldif) at /export/servers/ds72/etc/dirsrv/slapd-ID, by default.  If you have Directory Server(s) which configuration file is put at the other location, you need to input it to register the server.
>
>If you have such Directory Server, type the full path that stores the configuration file.
>
>If you don't, type return.
>[configuration directory path or return]:
>
>
>==============================================================================
>Candidate servers to register:
>    /export/servers/ds72/slapd-laputa2
>    /export/servers/ds72/etc/dirsrv/slapd-laputa
>    /export/servers/ds72/tmp/slapd-laputa3
>
>==============================================================================
>Do you want to use this server as Configuration Directory Server?
>
>Directory server identifier [laputa2]: laputa
>
>==============================================================================
>The server 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 server,
>create this user and group using your native operating
>system utilities.
>
>System User [nhosoi]:
>System Group [nhosoi]:
>
>==============================================================================
>Please specify the information about your configuration directory
>server.  The following information is required:
>- host (fully qualified), port (non-secure or secure), suffix,
>  protocol (ldap or ldaps) - this information should be provided in the
>  form of an LDAP url e.g. for non-secure
>ldap://host.example.com:389/o=NetscapeRoot
>  or for secure
>ldaps://host.example.com:636/o=NetscapeRoot
>- admin ID and password
>- admin domain
>- a CA certificate file may be required if you choose to use ldaps and
>  security has not yet been configured - the file must be in PEM/ASCII
>  format - specify the absolute path and filename
>
>Configuration directory server URL [ldap://laputa.sfbay.redhat.com:22222/o=NetscapeRoot]:
>Configuration directory server admin ID [admin]:
>Configuration directory server admin password:
>Configuration directory server admin password (confirm):
>Configuration directory server admin domain [sfbay.redhat.com]:
>
>==============================================================================
>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 [sfbay.redhat.com]:
>
>==============================================================================
>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.
>
>The default in brackets was randomly selected from the available
>ports on your system.
>
>Administration port [9830]: 12340
>
>==============================================================================
>Registering new Config DS: laputa
>
>==============================================================================
>Input the Directory Server password on the server laputa:
>
>==============================================================================
>Registering Sub DSes:
>==============================================================================
>If you want to register the server laputa2, input the Directory Manager password on the server.
>
>If you don't, type return.
>[Directory Manager password on laputa2 or return]:
>
>==============================================================================
>If you want to register the server laputa3, input the Directory Manager password on the server.
>
>If you don't, type return.
>[Directory Manager password on laputa3 or return]:
>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 . . .
>The admin server was successfully started.
>Admin server was successfully created, configured, and started.
>Finished registration of the Directory ServerExiting . . .
>Log file is '/tmp/setupjwttm7.log'

Actions: View

Attachments on bug 253811: 162024 | 162025 | 172383