[JIRA] Commented: (SSPCPP-517) Windows SP installer should not always roll back when shibd fails to start
Scott Cantor (JIRA)
noreply at shibboleth.net
Fri Nov 2 10:03:07 EDT 2012
[ https://issues.shibboleth.net/jira/browse/SSPCPP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533#comment-14533 ]
Scott Cantor commented on SSPCPP-517:
-------------------------------------
I can live with it, but would switching the predicate in the first case work? Seems like it should normally go ahead and start or fail, but if somebody has an issue we can tell them to use the command line option and override it?
I would say we could go with the same logic on upgrades, just do it by default, not if overridden.
> Windows SP installer should not always roll back when shibd fails to start
> --------------------------------------------------------------------------
>
> Key: SSPCPP-517
> URL: https://issues.shibboleth.net/jira/browse/SSPCPP-517
> Project: Shibboleth SP - C++
> Issue Type: Improvement
> Components: Installation / Packaging
> Affects Versions: 2.5.0
> Reporter: Elliot Kendall
> Assignee: Scott Cantor
> Priority: Minor
> Fix For: 2.5.1
>
> Original Estimate: 4 hours
> Time Spent: 1 hour
> Remaining Estimate: 3 hours
>
> The SP Windows installer currently installs the software, tries to start shibd, and then removes the software if shibd does not start. Troubleshooting the reason that shibd did not start generally requires that the SP software be installed, however.
> Either disable the rollback functionality completely, or provide an option (GUI or command line) to let the user disable it.
> See also:
> http://marc.info/?l=shibboleth-users&m=135057653113392
> https://issues.shibboleth.net/jira/browse/SSPCPP-499
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list