[
https://issues.apache.org/jira/browse/SOLR-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231845#comment-14231845
]
Timothy Potter commented on SOLR-6653:
--------------------------------------
[[email protected]] I fixed the issue you mentioned in SOLR-4792 as part of
this work. Now you can do:
{code}
cp -rp server s1
cd s1
../bin/solr start -e techproducts -d .
{code}
> bin/solr start script should return error code >0 when something fails
> ----------------------------------------------------------------------
>
> Key: SOLR-6653
> URL: https://issues.apache.org/jira/browse/SOLR-6653
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
> Affects Versions: 4.10.1
> Reporter: Jan Høydahl
> Assignee: Timothy Potter
> Labels: bin/solr
> Fix For: 4.10.3, 5.0
>
>
> In order to be able to include {{bin/solr}} in scripts, it should be possible
> to test the return value for success or failure. Examples:
> {noformat}
> jan:solr janhoy$ bin/solr start
> Waiting to see Solr listening on port 8983 [/]
> Started Solr server on port 8983 (pid=47354). Happy searching!
> jan:solr janhoy$ echo $?
> 0
> jan:solr janhoy$ bin/solr start
> Solr already running on port 8983 (pid: 47354)!
> Please use the 'restart' command if you want to restart this node.
> jan:solr janhoy$ echo $?
> 0
> {noformat}
> The last command should return status 1
> {noformat}
> jan:solr janhoy$ bin/solr stop -p 1234
> No process found for Solr node running on port 1234
> jan:solr janhoy$ echo $?
> 0
> {noformat}
> Same here. Probably other places too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
