[jira] [Updated] (SOLR-9047) zkcli should allow alternative locations for log4j configuration
[ https://issues.apache.org/jira/browse/SOLR-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-9047: --- Fix Version/s: (was: 6.0) master (7.0) Manually correcting fixVersion per Step #S5 of LUCENE-7271 > 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
[jira] [Updated] (SOLR-9047) zkcli should allow alternative locations for log4j configuration
[ https://issues.apache.org/jira/browse/SOLR-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Chanan updated SOLR-9047: - Attachment: SOLR-9047.patch Here's a patch that matches the caps style (I had been copying the style from solr.cmd) > 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 > 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
[jira] [Updated] (SOLR-9047) zkcli should allow alternative locations for log4j configuration
[ https://issues.apache.org/jira/browse/SOLR-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Chanan updated SOLR-9047: - Attachment: SOLR-9047.patch Here's a patch that lets you specify the log4j configuration file via the LOG4J_PROPS environment variable. I'd appreciate someone looking at the windows code since I can't test. > 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 > Attachments: 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