[JIRA] Assigned: (SSPCPP-517) Windows SP installer should not always roll back when shibd fails to start

[Rod Widdowson (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/SSPCPP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rod Widdowson reassigned SSPCPP-517:
------------------------------------

    Assignee: Scott Cantor  (was: Rod Widdowson)

Scott,
I'd like an OK on the proposed fix:

- Do not try to start on virgin install unless a specific property is set on the command line.

- Do try to start on an upgrade (regardless of the command line).

I am wondering whether this is either too complicated (and the answer should be "never try to start") or too simple (add a property to affect the second predicate).

The above fix has been tested and is ready to go (doesn't half speed up install), modulo the need to do upgrade testing when we do final test

> 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