nsTaskTotalItems This attributes shows the total number of subtasks that must be completed for the task operation. When the nsTaskCurrentItem attribute has the same value as nsTaskTotalItems, then the task is completed.

This attribute value is set by the server and should not be edited.

Parameter

Description

Entry DN

cn=task_name, cn=task_type, cn=tasks, cn=config

 

 

Valid Values

0 to the maximum 32 bit integer value (2147483647)

 

 

Default Value

 

 

 

Syntax

Integer

 

 

Example

nsTaskTotalItems: 152

 

 

nsTaskCancel This attribute allows a task to be aborted while in progress. This attribute can be modified by users.

Parameter

Description

Entry DN

cn=task_name, cn=task_type, cn=tasks, cn=config

 

 

Valid Values

true false

 

 

Default Value

 

 

 

Syntax

Case-insensitive string

 

 

Example

nsTaskCancel: true

 

 

ttl This attribute sets the amount of time (in seconds) the task entry will remain in the DSE after the task has finished or aborted. Setting a ttl attribute allows the task entry to be polled for new status information without missing the exit code. Setting the ttl attribute to 0 means that the entry is not cached.

Parameter

Description

Entry DN

cn=task_name, cn=task_type, cn=tasks, cn=config

 

 

Valid Values

0 (cannot be cached) to the maximum 32 bit integer value (2147483647)

 

 

Default Value

 

 

 

Syntax

DirectoryString

 

 

Example

ttl: 120

 

 

2.3.14.2 cn=import,cn=tasks,cn=config

An LDIF file or multiple LDIF files can be imported through 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 it removed from the directory.

The cn=import entry is a container entry for import task operations. The cn=import entry itself has no attributes, but each of the task entries within this entry, such as cn=task_ID, cn=import, cn=tasks, cn=config, uses the following attributes to define the import task.

An import task entry under cn=import must contain the LDIF file to import (in the “nsFilename” attribute) and the name of the instance into which to import the file (in the “nsInstance” attribute). Additionally, it must contain a unique cn to identify the task. For example:

100 Core server configuration reference