HP-UX Reference (11i v2 07/12) - 1M System Administration Commands A-M (vol 3)

l
ldapugadd(1M) ldapugadd(1M)
If this argument is not specified, the user will not be added to alternate groups.
-s login_shell Specifies the full path name to the executable that will be used to handle login sessions for
this user. If this argument is not specified, the default, as configured by
ldapugadd -D
-s
default_shell, will be used.
-d home_directory
Specifies the full path name (including the user name) of the user’s home directory. If this
argument is not specified, the combination of the default base directory, as configured by
ldapugadd -D -d default_home, and the user’s account name, will be used. If you
wish to also create the home directory on this system, the
-m option must specified.
-I gecos Specifies GECOS fields for the user. Typically the GECOS contains four fields which
represent (in 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 should be separated by a comma. If the data within the gecos field
contains any white space or other characters that might be parsed by the shell, the entire
string must be protected by enclosing quotes. White space should not be used between each
field and the separating commas.
Note that LDAP-UX supports mapping of the gecos field to multiple attributes. If attribute
mapping has been specified in the LDAP-UX configuration profile, each field will be mapped
to its representative attribute, in the order specified.
If
-I is not specified, the gecos attribute(s) will not be added to the user’s entry.
WARNING: If the -I option is specified and attribute mapping has been defined for the
gecos attribute, be careful not to specify the same attributes in the command line that are
also used in the gecos map. For example, suppose the gecos has been mapped to cn, l and
telephoneNumber. Because
-f below represents the cn attribute when creating new user
account entries, the following command might produce unpredictable results since cn is
specified by both
-f and by the gecos mapping:
ldapugadd -f "Jim Smith" \
-I "Jim Smith,Boston,555-12354" \
jsmith "sn=Smith" "telePhoneNumber=555-1234"
In the above example, because of the gecos attribute mapping, the cn and
telephoneNumbers are specified twice and will result an error when the same attribute and
value are added to the directory server
ldapcfinfo can be used to determine gecos attri-
bute mapping configuration.
NOTE: Since the gecos attribute may be mapped to one or several attributes, the number of
values specified with
-I (between the commas) should, but is not required to, match the
number of mapped attributes. If there are more mapped attributes than specified values in
-I, then trailing mapped attributes will not be added to the directory server. If there are
more values than mapped attributes, extra values will be combined in the last mapped
attribute.
-c comment Specifies a comment that will be stored in the description attribute, as defined by RFC2307.
Attribute mapping is not defined for the description attribute. If unspecified, the descrip-
tion attribute will not be added to the user’s entry. Since the comment field often contains
white-space, be sure to protect it from shell parsing with enclosing quote characters.
-T template_file
Specifies the LDIF template file that will be used to create new user entries. The
template_file parameter may either be a full or relative path name or a "short" name. Refer
to Template File Naming below for additional information.
uid_name Required Argument. Contains the POSIX-style textual login name for the new user
entry. This user name should conform to HP-UX login name requirements. Please refer to
passwd(4) for login name requirements.
uid_name is a required parameter, and it must follow all command-line options and must
precede the attr=value parameters (if provided).
466 Hewlett-Packard Company − 4 − HP-UX 11i Version 2: December 2007 Update