ldapugadd.1m (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

ldapugadd(1M) ldapugadd(1M)

If this argument is not speciﬁed, the user will not be added to alternate groups.

-s login_shell Speciﬁes the full path name to the executable that will be used to handle login sessions

for this user. If this argument is not speciﬁed, the default, as conﬁgured by

ldapugadd

-D -s default_shell, will be used.

-d home_directory

Speciﬁes the full path name (including the user name) of the user’s home directory. If

this argument is not speciﬁed, the combination of the default base directory, as

conﬁgured 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

speciﬁed.

-I gecos Speciﬁes GECOS ﬁelds for the user. Typically the GECOS contains four ﬁelds 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 ﬁeld in the gecos should be separated by a comma. If the data within the gecos ﬁeld

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 ﬁeld and the separating commas.

Note that LDAP-UX supports mapping of the gecos ﬁeld to multiple attributes. If attri-

bute mapping has been speciﬁed in the LDAP-UX conﬁguration proﬁle, each ﬁeld will be

mapped to its representative attribute, in the order speciﬁed.

-I is not speciﬁed, the gecos attribute(s) will not be added to the user’s entry.

WARNING: If the

-I option is speciﬁed and attribute mapping has been deﬁned 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

speciﬁed 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 speciﬁed 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

attribute mapping conﬁguration.

NOTE: Since the gecos attribute may be mapped to one or several attributes, the number

of values speciﬁed with

-I (between the commas) should, but is not required to, match

the number of mapped attributes. If there are more mapped attributes than speciﬁed

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 Speciﬁes a comment that will be stored in the description attribute, as deﬁned by

RFC2307. Attribute mapping is not deﬁned for the description attribute. If unspeciﬁed,

the description attribute will not be added to the user’s entry. Since the comment ﬁeld

often contains white-space, be sure to protect it from shell parsing with enclosing quote

characters.

-T template_file

Speciﬁes the LDIF template ﬁle that will be used to create new user entries. The

template_ﬁle 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.

4 Hewlett-Packard Company − 4 − HP-UX 11i v3: June 2010 Web Release