Red-hat 8.1 Uživatelský manuál stáhnout pdf (Strana 84)

Example nsImportChunkSize: 10

nsImport IndexAt trs

This attribute sets whether to index the attributes that are imported into database instance.

Parameter Descript ion

Entry DN cn=task_name, cn=import, cn=tasks, cn=config

Valid Values true | false

Default Value true

Syntax Case-insensitive string

Example nsImportIndexAttrs: true

nsUniqueIdGenerator

This sets whether to generate a unique ID for the imported entries. By default, this attribute generates

time-based IDs.

Parameter Descript ion

Entry DN cn=task_name, cn=import, cn=tasks, cn=config

Valid Values none (no unique ID) | empty (time-based ID) |

deterministic namespace (name-based ID)

Default Value empty

Syntax Case-insensitive string

Example nsUniqueIdGenerator:

nsUniqueIdGeneratorNamespace

This attributes defines how to generate name-based IDs; the attribute sets the namespace to use to

generate the IDs. T his option is useful to import the same LDIF file into two Directory Server instances

when the entries need to have the same IDs.

Parameter Descript ion

Entry DN cn=task_name, cn=import, cn=tasks, cn=config

Valid Values Any string

Default Value

Syntax Case-insensitive string

Example nsUniqueIdGeneratorNamespace: example

2.3.15.3. cn=export

A database or multiple databases can be exported 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 is removed from the directory.

The cn=export entry is a container entry for export task operations. The cn=export entry itself has

no attributes, but each of the task entries within this entry, such as cn=task_ID, cn=export,

cn=tasks, cn=config, uses the following attributes to define the export task.

An export task entry under cn=export must contain the name of the database to export (in the

nsInstance attribute) and the name of the LDIF file to write the output to (in the nsFilename attribute).

Additionally, it must contain a unique cn to identify the task. For example:

dn: cn=exam ple export, cn=export, cn=tasks, cn=config

objectclass: extensibleObject

cn: example export

nsInstance: userRoot

nsFilenam e: /home/files/example.ldif

As the export 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”.

There are some optional attributes which can be used to refine the export operation, similar to the

options for the db2ldif and db2ldif.pl scripts:

nsIncludeSuffix, analogous to the -s option, to specify the suffixes to include in the exported LDIF

files

nsExcludeSuffix, analogous to the -x option, to exclude the specified suffixes from the exported LDIF

files

nsUseOneFile, analogous to the -M option, to break up the exported suffixes into individual LDIF files

84 Chapter 2. Core Server Configuration Reference

1 2 ... 79 80 81 82 83 84 85 86 87 88 89 ... 291 292

Komentáře k této Příručce

Žádné komentáře

Red-hat 8.1 Uživatelský manuál Strana 84

Komentáře k této Příručce