LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Server Administrator's Guide (edition 8)

• The user’s work telephone number
• The user’s home telephone number (often omitted)
You must separate each field in the <gecos> argument by a
comma. If the data within the <gecos> argument contains any
white space or other characters that may be parsed by the shell,
you must protect the entire string by enclosing quotes. White
space cannot be used between the each field and the separating
commas.
LDAP-UX supports attribute mapping of the gecos attribute 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.
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 below 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
190 Command, Tool, Schema Extension Utility, and Migration Script Reference