Table of Contents
Advertisement
Recording Updates in the Change Log
You can decide to record updates in the replication change log instead of recording
them in the default location, that is in the
/usr/netscape/servers/slapd- serverID /logs
you want referential integrity updates to be replicated to consumer servers in the
context of replication.
You can make this change from the Directory Server Console.
From the Directory Server Console
On the Directory Server Console, select the Configuration tab.
1.
For information on starting the Directory Server Console, refer to "Using the
Directory Server Console," on page 28.
Expand the Plugins folder in the navigation tree, and select the Referential
2.
Integrity Postoperation plug-in.
The settings for the plug-in are displayed in the right pane.
In the arguments list, replace the
3.
the change log directory.
Click Save to save your changes.
4.
For your changes to be taken into account, go to the Tasks tab, and select
5.
Restart the Directory Server.
Modifying the Update Interval
By default, the server makes referential integrity updates immediately after a
or a
operation. If you want to reduce the impact this operation has
delete
modrdn
on your system, you may want to increase the amount of time between updates.
Although there is no maximum update interval, the following intervals are
commonly used:
•
Update immediately
•
90 seconds (updates occur every 90 seconds)
•
3600 seconds (updates occur every hour)
•
10,800 seconds (updates occur every 3 hours)
•
28,800 seconds (updates occur every 8 hours)
file in the
referint
directory. You must do this if
filename with the absolute path to
referint
Chapter 2
Maintaining Referential Integrity
Creating Directory Entries
71
Advertisement
Table of Contents
