[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Pki-devel] [PATCH] 259 - ticket 1414, option to not setup replication agreements

Turns out I already implemented this awhile back.

This small patch just updates the man page.


>From 0d3b5f07d691939e21c73d8dc6f60e12d833baf1 Mon Sep 17 00:00:00 2001
From: Ade Lee <alee redhat com>
Date: Fri, 10 Jul 2015 14:10:43 -0400
Subject: [PATCH] Ticket 1414: Add documentation of pki_clone_setup_replication

 base/server/man/man5/pki_default.cfg.5 | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/base/server/man/man5/pki_default.cfg.5 b/base/server/man/man5/pki_default.cfg.5
index 2c8dbbd45ee58303638ada8bc99cd2823f8cb30b..6623ce6fd5d5cf425bd93e73eb450d31b4f788bb 100644
--- a/base/server/man/man5/pki_default.cfg.5
+++ b/base/server/man/man5/pki_default.cfg.5
@@ -257,11 +257,15 @@ Installs a clone, rather than original, subsystem.
 Location and password of the PKCS #12 file containing the system certificates for the master subsystem being cloned.  This file should be readable by the user that the Certificate Server is running as (default of pkiuser), and have the correct selinux context (pki_tomcat_cert_t).  This can be achieved by placing the file in \fI/var/lib/pki/<instance_name>/alias\fP.
+.B pki_clone_setup_replication
+Defaults to True.  If set to False, the installer does not set up replication agreements from the master to the clone as part of the subsystem configuration.  In this case, it is expected that the top level suffix already exists, and that the data has already been replicated.  This option is useful if you want to use other tools to create and manage your replication topology, or if the baseDN is already replicated as part of a top-level suffix.
 .B pki_clone_replication_master_port, pki_clone_replication_clone_port
 Ports on which replication occurs.  These are the ports on the master and clone databases respectively.  Defaults to the internal database port. 
-.B pki_clone_repicate_schema
+.B pki_clone_replicate_schema
 Replicate schema when the replication agreement is set up and the new instance (consumer) is initialized.  Otherwise, the schema must be installed in the clone as a separate step beforehand.  This does not usually have to be changed.  Defaults to True.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]