Red Hat 8.1, Command Reference Manual

Page: 129 / 372

cn=tasks
115
Parameter Description
Valid Values Any local directory location
Default Value
Syntax
Case-exact string
Example nsArchiveDir: /export/backups
nsDatabaseTypes
This attribute gives the kind of database being archived. Setting the database types signals what kind
of backup plug-in the Directory Server should use to archive the database.
Parameter Description
Entry DN cn=
task_name
, cn=restore, cn=tasks, cn=config
Valid Values ldbm database
Default Value ldbm database
Syntax Case-exact string
Example nsDatabaseType: ldbm database
2.3.15.6. cn=index
Directory attributes can be indexed though the command line by creating a special task entry which
defines the parameters of the task and initiates the task. As soon as the task is complete, the task
entry is removed from the directory.
The
cn=index
entry is a container entry for index task operations. The
cn=index
entry itself has no
attributes, but each of the task entries within this entry, such as
cn=
task_ID
,
cn=index
,
cn=tasks
,
cn=config
, uses the following attributes to define the backup task.
An index task entry under
cn=index
can create a standard index by identifying the attribute to be
indexed and the type of index to create, both defined in the
nsIndexAttribute
attribute.
Alternatively, the index task can be used to generate virtual list view (VLV) indexes for an attribute
using the
nsIndexVLVAttribute
attribute. This is the same as running the
vlvindex
script.
For example:
dn: cn=example presence index, cn=index, cn=tasks, cn=config
objectclass: extensibleObject
cn: example presence index
nsIndexAttribute: "cn:pres"
dn: cn=example VLV index, cn=index, cn=tasks, cn=config
objectclass: extensibleObject
cn: example VLV index
nsIndexVLVAttribute: "by MCC ou=people,dc=example,dc=com"
As the index operation runs, the task entry will contain all of the server-generated task attributes listed
in
Section 2.3.15.1, “Task Invocation Attributes for Entries under cn=tasks”
.