diff options
| author | Matthew Harmsen <mharmsen@pki.usersys.redhat.com> | 2015-04-13 14:59:29 -0600 |
|---|---|---|
| committer | Matthew Harmsen <mharmsen@pki.usersys.redhat.com> | 2015-04-13 14:59:29 -0600 |
| commit | 18b24a990ff9b97cf58aa630af0084975fe4c130 (patch) | |
| tree | 1dc97c105c772000f9bc17edfac5c84d30248f22 /base/server/man | |
| parent | e57a2d410d19d72e902bd1792e01f1f238f2ed63 (diff) | |
| download | pki-18b24a990ff9b97cf58aa630af0084975fe4c130.tar.gz pki-18b24a990ff9b97cf58aa630af0084975fe4c130.tar.xz pki-18b24a990ff9b97cf58aa630af0084975fe4c130.zip | |
pki-tomcatd fails to start on system boot
- PKI TRAC Ticket #1315 - pki-tomcatd fails to start on system boot
- PKI TRAC Ticket #1340 - pkidestroy should not remove /var/lib/pki
Diffstat (limited to 'base/server/man')
| -rw-r--r-- | base/server/man/man5/pki_default.cfg.5 | 15 | ||||
| -rw-r--r-- | base/server/man/man8/pkispawn.8 | 7 |
2 files changed, 15 insertions, 7 deletions
diff --git a/base/server/man/man5/pki_default.cfg.5 b/base/server/man/man5/pki_default.cfg.5 index 1cf5c5134..ca8e095e4 100644 --- a/base/server/man/man5/pki_default.cfg.5 +++ b/base/server/man/man5/pki_default.cfg.5 @@ -206,6 +206,21 @@ Located in the [Tomcat] section, this variable determines whether the instance w .IP Sets whether to attach a Java debugger such as Eclipse to the instance for troubleshooting. Defaults to False. .PP +.B pki_enable_on_system_boot +.IP +Sets whether or not PKI instances should be started upon system boot. +.IP +Currently, if this PKI subsystem exists within a shared instance, and it has been configured to start upon system boot, then ALL other previously configured PKI subsystems within this shared instance will start upon system boot. +.IP +Similarly, if this PKI subsystem exists within a shared instance, and it has been configured to NOT start upon system boot, then ALL other previously configured PKI subsystems within this shared instance will NOT start upon system boot. +.IP +Additionally, if more than one PKI instance exists, no granularity exists which allows one PKI instance to be enabled while another PKI instance is disabled (i.e. - PKI instances are either all enabled or all disabled). To provide this capability, the PKI instances must reside on separate machines. +.IP +Defaults to True (see the following note on why this was previously 'False'). +.TP +\fBNote:\fP +Since this parameter did not exist prior to Dogtag 10.2.3, the default behavior of PKI instances in Dogtag 10.2.2 and prior was False. To manually enable this behavior, obtain superuser privileges, and execute '\fBsystemctl enable pki-tomcatd.target\fP'; to manually disable this behavior, execute '\fBsystemctl disable pki-tomcatd.target\fP'. +.PP .B pki_security_manager .IP Enables the Java security manager policies provided by the JDK to be used with the instance. Defaults to True. diff --git a/base/server/man/man8/pkispawn.8 b/base/server/man/man8/pkispawn.8 index 1d38b117a..1ef9b26be 100644 --- a/base/server/man/man8/pkispawn.8 +++ b/base/server/man/man8/pkispawn.8 @@ -514,13 +514,6 @@ To obtain a detailed status of all Tomcat PKI instances: \fBpkidaemon status tomcat\fR .fi -.PP -To enable a PKI instance named <pki_instance_name> to be started automatically upon system reboot: -.IP -.nf -\x'-1'\fBsystemctl enable pki-tomcatd@<pki_instance_name>.service\fR -.fi - .SH BUGS Report bugs to http://bugzilla.redhat.com. |