[ 
https://issues.apache.org/jira/browse/SOLR-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Høydahl updated SOLR-11853:
-------------------------------
    Fix Version/s:     (was: 7.6)
                   7.7

> Solr installer fails on SuSE linux (Make check for used tool "service" 
> compatible with SuSE Linux like OpenSuse or SLES)
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-11853
>                 URL: https://issues.apache.org/jira/browse/SOLR-11853
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: scripts and tools
>    Affects Versions: 7.0, 7.0.1, 7.1, 7.2, 7.2.1, 7.3, 7.3.1, 7.4, 7.5
>         Environment: SuSE Linux (SLES & OpenSuSE)
>            Reporter: Markus Mandalka
>            Assignee: Jan Høydahl
>            Priority: Minor
>              Labels: github-import, newbie, patch
>             Fix For: master (8.0), 7.7
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> On current SuSE Linux releases like SLES or OpenSuSE the Solr installer stops 
> with the error message "Script requires the 'service' command".
> This happens because before installation the installer checks if the used 
> command "service" exists by its option "service --version".
> The command line option "--version" doesn't exist for "service" on current 
> SuSE Linux stable releases.
> Since the command "service" is there and has an option "--help", this option 
> can be used as additional fallback.
> So in the pull request i extended the check with "service --help" as second 
> check / fallback before printing this error and exiting.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to