Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
2.4.3 ndsd Falls Back to Default Port if the Interface Specified<br />
is Incorrect<br />
When using ndsconfig new or ndsmanage to create a second instance of the directory, if the interface<br />
specified is incorrect, nds tries to use the default interface. If you specify non default port (for<br />
example 1524), the interface specified is incorrect, it uses the default interface and the default port<br />
of 524.<br />
novdocx (en) 22 June 2009<br />
For n4u.server.interfaces, if the interface specified is incorrect, then ndsd will try to listen on the first<br />
interface and the port number would be the one specified in n4u.server.tcp-port.<br />
2.4.4 How to Rebuild .eDir Directory<br />
The .edir directory is used for tracking multiple instances of <strong>eDirectory</strong>. To recreate the lost or<br />
corrupted instances file (instances.$uid file, where $uid specifies the user ID of the user in the<br />
system), you must create its individual instances file.<br />
These files must contain the absolute location of the nds.conf files of all the instances configured by<br />
the user. For example, a user with uid as 1000 must create /etc/opt/novell/<strong>eDirectory</strong>/conf/<br />
.edir/instances.1000 instances file with the following entries:<br />
/home/user1/instance1/nds.conf<br />
/home/user1/instance2/nds.conf<br />
20 <strong>Novell</strong> <strong>eDirectory</strong> <strong>8.8</strong> <strong>Troubleshooting</strong> <strong>Guide</strong>
Change language