lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Chanan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-9047) zkcli should allow alternative locations for log4j configuration
Date Thu, 28 Apr 2016 02:22:12 GMT

    [ https://issues.apache.org/jira/browse/SOLR-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261416#comment-15261416
] 

Gregory Chanan commented on SOLR-9047:
--------------------------------------

bq. is it time to just kill zkcli and move it's functionality into bin/solr ?

probably :).  In any case that would be a 7.x change, right?  This would be useful in 6.x
imo.

> 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
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message