6.7.4 eDirectory Not Restarting Automatically
After a system crash or power failure, eDirectory services (ndsd) might not automatically restart in
some situations. To start eDirectory again, do the following:
1 Delete the
2 At a terminal prompt, enter
6.7.5 One Instance Only
OES 2 supports only one instance of eDirectory (meaning one tree instance) per server.
If you need two or more instances running on a single server, you must install them on a non-OES
server, such as SLES 10.
6.7.6 Special Characters in Usernames and Passwords
Using special characters in usernames and passwords can create problems when the values are
passed during an eDirectory installation or schema extension.
If the username or password contains special characters, such as $, #, and so on, escape the character
by preceding it with a backslash (\). For example, an administrator username of
cn=admin$name.o=container
must be passed as
cn=admin\$name.o=container
When entering parameter values at the command line, you can either escape the character or place
single quotes around the value. For example:
cn=admin\$name.o=container
or
'cn=admin$name.o=container'
6.8 iFolder 3.8
Implementation caveats for iFolder 3.8 are documented in
Services" in the
6.9 iPrint
iPrint has the following implementation caveats:
Section 6.9.1, "Cluster Failover Between Mixed Platforms Not Supported," on page 65
Section 6.9.2, "Printer Driver Uploading on OES 2 Might Require a CUPS Administrator
Credential," on page 65
Section 6.9.3, "Printer Driver Uploading Support," on page 65
Section 6.9.4, "iManager Plug-Ins Are Platform-Specific," on page 65
64
OES 2 SP3: Planning and Implementation Guide
/var/opt/novell/eDirectory/data/ndsd.pid
/etc/init.d/ndsd start.
Novell iFolder 3.8.4 Administration
file.
"Caveats for Implementing iFolder
Guide.
Need help?
Do you have a question about the OPEN ENTERPRISE SERVER - PLANNING AND IMPLEMENTATION GUIDE 12-2010 and is the answer not in the manual?
Questions and answers