HP-UX Directory Server 8.1 configuration, command, and file reference

dn: cn=example import, cn=import, cn=tasks, cn=config
objectclass: nsDirectoryServerTask
cn: example import
nsFilename: /home/files/example.ldif
nsInstance: userRoot
As the import operation runs, the task entry will contain all the server-generated task attributes
listed in “Task invocation attributes for entries under cn=tasks”.
There are some optional attributes which can be used to refine the import operation, similar to
the options for the ldif2db and ldif2db.pl scripts:
• “nsIncludeSuffix”, which is analogous to the -s option to specify the suffix to import
• “nsExcludeSuffix”, analogous to the -x option to specify a suffix or subtree to exclude from
the import
• “nsImportChunkSize”, analogous to the -c option to override starting a new pass during
the import and merge the chunks
• “nsImportIndexAttrs”, which sets whether to import attribute indexes (with no corollary
in the script options)
• “nsUniqueIdGenerator”, analogous to the -g option to generate unique ID numbers for the
entries
• “nsUniqueIdGeneratorNamespace”, analogous to the -G option to generate a unique,
name-based ID for the entries
nsFilename The nsFilename attribute contains the path and file names of the LDIF files to
import into the Directory Server instance. To import multiple files, add multiple instances of this
attribute. For example:
nsFilename: file1.ldif
nsFilename: file2.ldif
DescriptionParameter
cn=task_name, cn=import, cn=tasks, cn=config
Entry DN
Any stringValid Values
Default Value
Case-exact string, multi-valuedSyntax
nsFilename: /home/jsmith/example.ldifExample
nsInstance This attribute supplies the name of the database instance into which to import the
files, such as NetscapeRoot or slapd-example
DescriptionParameter
cn=task_name, cn=import, cn=tasks, cn=config
Entry DN
The name of a Directory Server instance (any string)Valid Values
Default Value
Case-exact stringSyntax
nsInstance: userRootExample
2.3 Core server configuration attributes reference 101