LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS

If you do not specify the -I option, ldapugadd does not add
the <gecos> attribute to the user entry.
WARNING! If you specify the -I option and you have defined
attribute mapping for the gecos attribute, be careful not to specify
the same attributes in the command line that are also used in the
gecos map. In the following example, if the gecos attribute has
been mapped to cn, l, and telephoneNumber. Because -f
represents the cn attribute when creating new user account entry,
the following command can produce unpredictable results because
cn is specified by both -f and the gecos mapping.
ldapugadd -f “Jim Bailey” -I “Jim
Bailey,Boston,555-1234” jbailey \
“sn=Bailey” “telePhoneNumber=555-1234”
In this example, because of the gecos attribute mapping, the cn
and telephoneNumber attributes are specified twice. The
ldapugadd tool results an error when the same attribute and
value are added to the directory server.
Use the ldapcfinfo tool to determine gecos attribute mapping
configuration.
NOTE: Because the gecos attribute may be mapped to one or
more 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 are not
added to the directory server. If more values than mapped
attributes exist, extra values are combined in the last mapped
attribute.
-c <comment> Optional. Specifies a comment that will be stored in the
description attribute as defined by RFC 2307. LDAP-UX does
not support attribute mappings for the description attribute. If
you do not specify this option, the description attribute is not
added to the user entry. Because the field often contains white
spaces, you must protect it from shell parsing by enclosing it in
quote characters. For example:
-c “example description”
-T <template_file> Optional. Specifies the LDIF template file to be used to create new
user entries. The <template_file> parameter may be a full or
relative path name or a short name. A short name is defined as
the distinguishing portion of the template file name. For example,
for the passwd service, if the short name “operator” is specified,
the resulting template file is /etc/opt/ldapux/
ug_templates/ug_passwd_operator.tmpl. All LDAP-UX
default template files are stored in the /etc/opt/ldapux/
ug_templates directory. A full or relative path name must begin
with a slash (/) or a period (.) character.
If you do not specify this argument, ldapugadd uses the default
template file /etc/opt/ldapux/ug_templates/
ug_passwd_default.tmpl.
302 Command and tool reference