One of my servers shows like command-line:
# netstat -anp | grep LISTEN | grep ndsd tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 16718/ndsd tcp 0 0 127.0.0.1:8389 0.0.0.0:* LISTEN 16718/ndsd tcp 0 0 192.168.1.4:8389 0.0.0.0:* LISTEN 16718/ndsd tcp 0 0 192.168.1.4:524 0.0.0.0:* LISTEN 16718/ndsd tcp 0 0 127.0.0.1:524 0.0.0.0:* LISTEN 16718/ndsd tcp 0 0 0.0.0.0:636 0.0.0.0:* LISTEN 16718/ndsd tcp 0 0 127.0.0.1:8636 0.0.0.0:* LISTEN 16718/ndsd tcp 0 0 192.168.1.4:8636 0.0.0.0:* LISTEN 16718/ndsdI have made a habit of putting DHOST on (http)8389 and (https)8636 so I might remember where it is running.
# ndslogin -t willeketree -h 192.168.1.4 jim.butler.people.willeke.com Password: eDirectory Login: logged in as .CN=jim.OU=butler.OU=people.dc=willeke.dc=com.WILLEKETREE.
# ps -eaf |grep ndsdTypical output would be:
root 5067 1 0 00:54 ? 00:00:00 /usr/sbin/ndsd root 5070 5067 0 00:54 ? 00:00:00 /usr/sbin/ndsd root 5071 5070 0 00:54 ? 00:00:00 /usr/sbin/ndsd root 5072 5070 0 00:54 ? 00:00:00 /usr/sbin/ndsd root 5074 5070 0 00:54 ? 00:00:00 /usr/sbin/ndsd root 5075 5070 0 00:54 ? 00:00:01 /usr/sbin/ndsd
These threads are Light Weight Processes (LWPs), which reduces switching overhead. You will see them as multiple ndsd's running on same machine. You can use pstree to see them as a structure view.
For example on 8.7.x,
pstree 'cat /var/nds/ndsd.pid'
pstree -G `cat /var/opt/novell/eDirectory/data/ndsd.pid`