Original issue 87 created by shvachko on 2014-09-29T22:03:24.000Z:
Right now Giraffa client logs are printed to console and the already existing logs directory for Giraffa is empty. Attached patch creates a new log4j.properties for Giraffa and defaults the following:
The first one defaults logging to the log file and the second one defaults not logging security logs, as per what the hdfs scripts do. Of course these environment variables can be changed via, for example, giraffa-env.sh.
Script messages (HADOOP_HOME location, etc.) still print and slf4j multiple bindings error message still prints but that's a separate issue.
Original issue 87 created by shvachko on 2014-09-29T22:03:24.000Z:
Right now Giraffa client logs are printed to console and the already existing logs directory for Giraffa is empty. Attached patch creates a new log4j.properties for Giraffa and defaults the following:
GIRAFFA_ROOT_LOGGER=INFO,RFA GIRAFFA_SECURITY_LOGGER=INFO,NullAppender
The first one defaults logging to the log file and the second one defaults not logging security logs, as per what the hdfs scripts do. Of course these environment variables can be changed via, for example, giraffa-env.sh.
Script messages (HADOOP_HOME location, etc.) still print and slf4j multiple bindings error message still prints but that's a separate issue.