#312 Dogtag 10: Automatically restart any running instances upon RPM "update" . . .
Closed: Fixed None Opened 11 years ago by mharmsen.

Per the following TRAC tickets, Dogtag 10 was corrected to allow previous Dogtag 9 instances to function correctly under Dogtag 10 packages:

* TRAC Ticket #301 - Need to modify init scripts to verify needed symlinks
  in an instance
* TRAC Ticket #303 - Dogtag 10: CS.cfg parameters for Dogtag 9 instance
  running under Dogtag 10 packages . . .

Although both of these tickets have been resolved, it is still necessary to perform a manual restart on any Dogtag 9 instance once the Dogtag 10 packages have been installed. It has been requested to integrate logic into the Dogtag 10 packages which traverses the Dogtag 9 registry, checks to see if that instance is running, and if so, to automatically issue a "restart" of that instance.


Resolved:

commit 7e5bfee6063bf53f3bbfd20b6e93df0b1a9b2843
Author: Matthew Harmsen <mharmsen@redhat.com>
Date:   Tue Sep 11 19:02:02 2012 -0700

    Restart existing instances upon package update

    * TRAC Ticket #312 - Dogtag 10: Automatically restart any running instances
      upon RPM "update" . . .
    * TRAC Ticket #317 - Dogtag 10: Move "pkispawn"/"pkidestroy"
      from /usr/bin to /usr/sbin . . .

Metadata Update from @mharmsen:
- Issue assigned to mharmsen
- Issue set to the milestone: Dogtag 10.0.0.a1

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/883

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata