Error: "line 334: ndsconfig: command not found" when adding eDirectory 8.8 instance with ndsmanage.

(Last modified: 22Dec2005)

This document (10100008) is provided subject to the disclaimer at the end of this document.

symptom

Error: "line 334: ndsconfig: command not found" when adding eDirectory 8.8 instance with ndsmanage.

fact

SUSE Linux Enterprise Server 9

Novell eDirectory 8.8

cause

ndsmange is run with the absolute path similar to the following and the session PATH variable is not set to the /opt/novell/eDirectory/bin directory:
`/opt/novell/eDirectory/bin/ndsmange`

When the ndsmanage script calls the ndsconfig command without a full path and the OS path is not referring to the correct directory the ndsconfig command is not found or run.

fix

This can be resolved either by setting the session's path and exporting that path for all child processes or else by preceeding the ndsmanage script with nsdpath.  The latter example follows (presumes that ndspath is called from the eDirectory binary directory):
./ndspath ndsmanage

note

At the end of the initial eDirectory 8.8 installation the user is prompted to set the PATH statements appropriately for all eDirectory binaries.  If these are not set and exported properly then accessing the eDirectory binaries must be done via absolute path or by preceeding them all with the ndspath command which exports the eDirectory path for commands run as parameters of ndspath.

document

Document Title: Error: "line 334: ndsconfig: command not found" when adding eDirectory 8.8 instance with ndsmanage.
Document ID: 10100008
Solution ID: NOVL104637
Creation Date: 20Dec2005
Modified Date: 22Dec2005
Novell Product Class:novell directory services

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.