ldapugadd.1m (2010 09)

ldapugadd(1M) ldapugadd(1M)

RETURN VALUE

Upon exit, ldapugadd returns the following:

0 Success.

ldapugadd exits with no errors or with one or more warnings.

<>0

ldapugadd returns with a non-zero exit status if it encounters an error, and messages will be

logged to stderr.

Messages will follow the below format:

ERROR: code

message

WARNING: code

message

Leading extra white space may be inserted to improve readability and follow 80 column screen

formatting.

code will be a programmatically parsable error key-string, while

message will be human-readable. Refer to the LDAP-UX Client Services Administrator’s Guide

for a list of possible error codes generated by the LDAP user and group management

tools.

LIMITATIONS

• Since LDAP directories require data be stored according to the UTF-8 (RFC3629) character encoding

method, all characters passed into

ldapugadd are assumed to UTF-8, and part of the ISO-10646

character set. ldapugadd does not perform conversion of the locale character set to/from the UTF-8

character set.

• Since

ldapugadd calls functions to discover if groups exists before adding a user to a group, it is pos-

sible to encounter timing issues with cached information. For example, if an administrator wishes to

see if a group exists by using grget, this group information will be cached by both ldapclientd (1M)

and pwgrd(1M).

If the group does not exist when calling

grget, and the administrator shortly there after creates this

group with ldapugadd, the information that the group still does not exist will still be cached. Then,

when adding a new user and specifying that this user is a member of the just created group, an error

will be generated to indicate the user can not be added to the group. To resolve this, the

pwgrd and

ldapclientd caches must be ﬂushed.