Installation guide

Configuring NetIQ eDirectory on Linux 85
As the name indicates, the pre_ndsd_start script is executed before the ndsd binary is started by the
/etc/init.d/ndsd script. The post_ndsd_start script is executed after the ndsd binary is started
by the
/etc/init.d/ndsd script. Similarly, the pre_ndsd_stop and post_ndsd_stop scripts are
executed before and after stopping the ndsd process, respectively.
You can add commands of your choice to these scripts to get them executed. By default, the
post_ndsd_start script has commands to ensure that /etc/init.d/ndsd comes out after ensuring
that the LDAP services are up and running.
NOTE: You must add all the environment variables required for the eDirectory service in the
pre_ndsd_start_custom script. Exporting of environment variables on terminals or /etc/init.d/
ndsd script is not used by eDirectory.
Using eDirectory on SLES 12 and RHEL 7 Platforms
eDirectory starts the daemon when the system starts with the configuration parameters from the
default configuration file,
/etc/opt/novell/eDirectory/conf/nds.conf .
Before starting ndsd, ensure that any SLP (Service Location Protocol) agent is running on the host.
You can install OpenSLP, any native SLP available with your operating system, or NetIQ SLP.
To start or stop eDirectory, use the ndsmanage utility.
The eDirectory configuration creates the following shell scripts in the
/opt/novell/eDirectory/
sbin
location:

pre_ndsd_start_custom : Use this script for custom addition of commands before executing
eDirectory.

post_ndsd_start_custom : Use this script for custom addition of commands after executing
eDirectory.

post_ndsd_stop_custom : Use this script for custom addition of commands after stopping
eDirectory.
NOTE: Do not use any of the factory scripts from the /opt/novell/eDirectory/sbin / location. The
eDirectory configuration will use the factory scripts. To include additional commands of your choice,
use custom scripts.
7.2 Configuration Parameters
The eDirectory configuration parameters are stored in the nds.conf file.
When configuration parameters are changed, ndsd needs to be restarted for the new value to take
effect. You should use ndsmanage to restart ndsd.
However, for some configuration parameters, ndsd need not be restarted. These parameters are listed
below:

n4u.nds.inactivity-synchronization-interval
 n4u.nds.synchronization-restrictions
 n4u.nds.janitor-interval
 n4u.nds.backlink-interval
 n4u.nds.drl-interval