LDAP-UX Client Services B.05.00 Administrator's Guide

NOTE: The dapugmod tool does not modify the user’s group
membership when chaining the primary group ID. Adding the
user as a member of the new group and possibly removing the
member from the previous group must be done with separate
ldapudmod operations.
-s <login_shell>
Replaces the full path name to the executable that is used to handle
login sessions for this user.
If the <login_shell> argument is an empty string (a pair of
double quotes: ""), ldapugmod removes the loginShell or
mapped attribute.
The ldapudmod tool issues a WARNING if the specified login
shell does not exist on the local system. See the “WARNING”
section below for impacts when using this option.
-d <home_directory>
Replaces the full path name (including the user name) of the user’s
home directory. If the <home_directory> argument is an empty
string (a pair of double quotes: ""), ldapugmod removes the
homeDirectory or mapped attribute.
-m
Move the user’s home directory to the location specified with the
-d option. -m requires that you also specify the -d option. If the
specified <home_directory> already exists, the user’s current
home directory does not exist or the user running ldapugmod
does not have sufficient permissions to move the directory,
ldapugmod returns an error.
-I <gecos> Replaces gecos fields for the user. If <gecos> is an empty string,
ldapugmod removes the gecos or mapped attribute(s).
Typically the gecos argument contains four fields which represent
in the following order:
• The user’s full name
• The user’s work location
• The user’s work telephone number
• The user’s home telephone number (often omitted)
Each field in the <gecos> argument must be separated by a
comma. Although the fields specified within the <gecos>
argument can contain white space (such as “Bill Smith,Building
6,555-1234”). White space cannot be used between each field and
the separating commas.
LDAP-UX supports attribute mapping of the gecos field to
multiple attributes. If attribute mapping has been specified in the
LDAP-UX configuration profile, each field is mapped to its
representative attribute, in the order specified.
254 Command and tool reference