[
https://issues.apache.org/jira/browse/SOLR-10055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-10055:
-------------------------------
Attachment: SOLR-10055.patch
Attaching patch which will rename said files on install. Tested on a clean
Debian system. Will commit soon
> Manual bin/solr start causes crash due to resolving wrong solr.in.sh
> --------------------------------------------------------------------
>
> Key: SOLR-10055
> URL: https://issues.apache.org/jira/browse/SOLR-10055
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Fix For: 6.5, master (7.0)
>
> Attachments: SOLR-10055.patch
>
>
> The install script installs {{solr.in.sh}} in {{/etc/defaults/}}. However, if
> the user manually runs {{solr start}}, the script will use the {{solr.in.sh}}
> file from {{bin/}} since that is first in the search path. And it will fail
> since {{/opt/solr}} is write protected. But if user starts with {{service
> solr start}} then the file from installation is used and all is fine.
> Since the default {{/opt/solr/server/solr}} is not writable by solr user,
> this creates a bad user experience and classifies as a bug.
> My proposal is that the installer renames {{bin/solr.in.sh ->
> bin/solr.in.sh.orig}} and the same with {{solr.in.cmd}}, so that the
> resolution logic will end up finding the one from the install. User can still
> override this by creating a {{$HOME/.solr.in.sh}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
