[
https://issues.apache.org/jira/browse/SOLR-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337377#comment-15337377
]
ASF subversion and git services commented on SOLR-9047:
-------------------------------------------------------
Commit c64b1194af9328c4da7bc5f5f08cbac93db3e7bf in lucene-solr's branch
refs/heads/branch_5x from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c64b119 ]
SOLR-9047: Remove misplaced CHANGES entry
> zkcli should allow alternative locations for log4j configuration
> ----------------------------------------------------------------
>
> Key: SOLR-9047
> URL: https://issues.apache.org/jira/browse/SOLR-9047
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools, SolrCloud
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
> Priority: Minor
> Fix For: 6.1, master (7.0)
>
> Attachments: SOLR-9047.patch, SOLR-9047.patch
>
>
> zkcli uses the log4j configuration in the local directory:
> {code}
> sdir="`dirname \"$0\"`"
> PATH=$JAVA_HOME/bin:$PATH $JVM
> -Dlog4j.configuration=file:$sdir/log4j.properties -classpath
> "$sdir/../../solr-webapp/webapp/WEB-INF/lib/*:$sdir/../../lib/ext/*"
> org.apache.solr.cloud.ZkCLI ${1+"$@"}
> {code}
> which is a reasonable default, but often people want to use a "global" log4j
> configuration. For example, one may define a log4j configuration that writes
> to an external log directory and want to point to this rather than copying it
> to each source checkout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
