ldapugadd.1m (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

ldapugadd(1M) ldapugadd(1M)

uid_name is a required parameter, and it must follow all command-line options and must

precede the attr =value parameters (if provided).

-m Create a new home directory for the deﬁned user. User and group ownership of the

newly created directory will be assigned to the user and his/her primary login group.

-k is speciﬁed, the ﬁles and sub-directories found in skel_dir will be copied to the

user’s home directory, and user and group ownership permissions altered as speciﬁed

above. If

-k is not speciﬁed, skeleton ﬁles will be copied from

/etc/skel.

The

-m option requires the user has sufﬁcient privilege to create the new home directory,

copy skeleton ﬁles and change ownership of those ﬁles and directories.

ldapugadd will

create a user’s home directory only after successfully adding the user’s entry in the direc-

tory server.

ldapugadd is unable to properly create the user’s home directory, per the above pro-

cess, the newly created changes in the directory server will not be removed. See Security

Consideration below for more information.

-k skel_dir -k is ignored unless the

-m option is speciﬁed. skel_dir speciﬁes a directory which con-

tains skeleton ﬁles and directories that should be copied into newly created user home

directories. See

-m above.

attr

=value Allows speciﬁcation of arbitrary LDAP attributes and values. Because of potential

objectclass requirements, additional information beyond the basic POSIX account and

group data may be need to be speciﬁed in order to create new entries in the directory

server.

For example, if the "InetOrgPerson" objectclass is used as a structural class for posixAc-

counts , then the sn (surname) attribute must be speciﬁed in order to properly create a

new entry. This value would need to be deﬁned in the template ﬁle (see Template Files ),

and would need to be speciﬁed at the end of the

ldapugadd command line.

The attr

=value parameter is generally used to specify attributes required by the tem-

plate ﬁle. However, if an attribute is speciﬁed which is not deﬁned in the deﬁned tem-

plate ﬁle, that attribute/value pair will be considered as an optional attribute/value which

will be added to the entry exactly as speciﬁed.

attr

=value parameters are optional, but must be speciﬁed as the last parameters on the

command line.

Arguments Applicable to ’-t group’

-g gid_number

Speciﬁes the group’s numeric id number. If the speciﬁed gidNumber already exists in the

directory server,

ldapugadd will not add the new entry and return an error exit status,

unless the -F option is speciﬁed.

If this argument is not speciﬁed, a new group ID number will be provisioned by randomly

selecting a value from the gidNumber range speciﬁed by

ldapugadd -d -g

min_gid:max_gid.Ifldapugadd randomly selects a gidNumber that is already in use

on the directory server, ldapugadd will randomly select another gidNumber and try

again until it ﬁnds an unused gidNumber or exhausts retry attempts. Retry attempts

will be limited to 90% of the range of available gidNumbers (speciﬁed with -D -g

min_gid:max_gid and described above).

-x domain Speciﬁes the group’s domain name. This variable is used to specify the ${domain } value

that can be used in the template ﬁle. If this value is not speciﬁed, the domain name will

be created by using the ﬁrst "dc" component of the new group’s distinguished name. If the

distinguished name does not contain any "dc" components, and the ${domain } variable

is speciﬁed in the template ﬁle, ldapugadd will generate an error.

-M member[,...]

Deﬁnes initial group membership by adding the speciﬁed user accounts as members. The

members must be deﬁned as a comma-separated list of account names, similar to the -G

requirements deﬁned above. Use of -M requires that the speciﬁed user’s account already

be deﬁned in the directory server, unless the -F option is speciﬁed.

When the

-F option is used, the users group membership will be deﬁned using the mem-

berUid attribute, regardless of the attribute mapping conﬁguration deﬁned by ldapux (5).

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