[
https://issues.apache.org/jira/browse/KAFKA-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506190#comment-13506190
]
David Arthur edited comment on KAFKA-637 at 11/29/12 3:48 AM:
--------------------------------------------------------------
Something like this?
I can now invoke the bin script like:
LOG4J_OPTS="-Dlog4j.debug=true
-Dlog4j.configuration=file:config/log4j.properties" ./bin/kafka-server-start.sh
config/server.properties
was (Author: mumrah):
Something like this?
I can now invoke the bin script like:
{code}
LOG4J_OPTS="-Dlog4j.debug=true
-Dlog4j.configuration=file:config/log4j.properties" ./bin/kafka-server-start.sh
config/server.properties
{code}
> Separate log4j environment variable from KAFKA_OPTS in kafka-run-class.sh
> -------------------------------------------------------------------------
>
> Key: KAFKA-637
> URL: https://issues.apache.org/jira/browse/KAFKA-637
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.8.1
> Reporter: Chris Curtin
> Priority: Minor
> Attachments: KAFKA-637.patch
>
>
> The kafka-run-class.sh script has an environment variable for 'KAFKA_OPTS'
> which defines the log4j configuration file with other system variables.
> By moving the log4j settings into their own variable we can set that
> configuration file without having to also include the system parameters. This
> way if the script changes in the next release our management scripts won't
> have (potentially) unexpected side effects.
> We change the logging configuration file in the test environment so we can
> run multiple brokers on a single machine for testing. Without this option all
> the logs for all the brokers get jumbled together.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
