Chapter 14   Starting, Stopping, and Restarting iDAR


This chapter describes how to start, stop, and restart iPlanet Directory Access Router (iDAR) from the command line. To do the same from the console, see Chapter 4 "Starting, Restarting, and Stopping iDAR."

This chapter contains the following sections:

• Starting and Stopping iDAR

• Supported Flags

• Restarting iDAR

Starting and Stopping iDAR

---

iDAR program runs as a UNIX daemon process or an NT service normally started during system boot time.

On all platforms, iDAR's start program resides at:

<server-root>/idar-<hostname>/start-idar

The startup configuration file resides at:

<server-root>/idar-<hostname>/etc/tailor.txt

iDAR may be started and stopped via the scripts found at:

<server-root>/idar-<hostname>

The Windows NT Service Manager should be used to start and stop iDAR on Windows NT. On platforms other than Windows NT, iDAR will produce only a core image in case of a crash if its effective user ID is same as its real user ID. Therefore, if you want iDAR to produce a core, then you must set the ids-proxy-con-userid attribute in object class ids-proxy-sch-GlobalConfiguration to the same user who starts the iDAR process. By default, if iDAR is run by root, it changes its userid to nobody.

Supported Flags

---

The flags supported by the start and stop scripts are described in Table 14-1.

Table 14-1    Flags Supported By the Start and Stop Scripts  

Flag	Description
-d	When this flag is present, iDAR will handle only a single incoming connection at a time, and will send more detailed internal tracing information to the log file. This flag should not be used during normal operation, because it will prevent the iDAR daemon from detaching from the controlling terminal.
-D	This flag tells iDAR to send more detailed tracing information to the log file. iDAR will still handle multiple client connections and run as a daemon. The -d and -D flags should be treated as mutually exclusive.
-I	This flag is applicable only on Windows NT, and is ignored on all other platforms. This flag must be used when starting iDAR program ldapfwd from the command line. The -d flag should be used in conjunction with the -I flag on Windows NT to get the debug output.
-t <startup configuration file>	This option can be used to specify an alternate startup configuration file.
-s	This option tells iDAR to send the initial log messages to the syslogd using the LOG_DAEMON facility. This flag is ignored on Windows NT. This is the default if the environment variable IDAR_ROOT is not defined.
-M	If this flag is specified, iDAR will spawn another process to monitor itself. In the case where iDAR exits ungracefully, the monitor process restarts iDAR after waiting for 30 seconds. This is not available on Windows NT.
-v	This flag prints the version information for iDAR. On Windows NT, this flag should be used from the command line only.

Restarting iDAR

---

On UNIX platforms, iDAR can be sent a SIGHUP signal to make it re-read its configuration. If the configuration is re-read successfully, iDAR will use this new configuration for future connections. Client connections that are already established will continue to use the old configuration until the clients disconnect.

To signal iDAR to re-read its configuration, use the hup-idar command found at <server-root>/idar-<hostname>.

Some attribute values cannot be changed using the HUP signal facility. For changes to the following configuration parameters, iDAR will have to be shut down and started again. These attributes include:

   ids-proxy-con-listen-port
   ids-proxy-con-listen-host
   ids-proxy-con-ldaps-port
   ids-proxy-con-foreground
   ids-proxy-con-listen-backlog
   ids-proxy-con-ssl-cert
   ids-proxy-con-ssl-key

Also, the logging properties ids-proxy-sch-LogProperty cannot be changed using this facility.

On all platforms, a restart-idar command is found at <server-root>/idar-<hostname>. The restart command simply invokes the stop-idar and start-idar commands found in the aforementioned directory.