I've attempted to modify the location of the log4j file for a bamboo agent, but without success.

• According to http://confluence.atlassian.com/display/BAMBOO/Logging+in+Bamboo, this can be done by adding an environment variable log4j.configuration or log4j.appender.fileLog.file. I've tried these with -D command line arguments, unix shell exports, inclusion in the bamboo-agent.cfg file and even as an agent capability. Although no approach actually works properly, the -D approach is the most successful. It starts out with the agent log in the correct place but then indicates that it's launching a remote agent, after which the output is generated into an atlassian-bamboo.log file in the root. I think the agent is launching a new process and forgetting to pass on environment variables.

Two comments about the aforementioned documentation link:

• It omits to specify that the /path/to/log4j.properties value should be specified as a url (ie file:///path/to/log4j.properies).
• It specifies that this data can be aded to the bamboo-agent.cfg file but omits to specify how and where in the file this should be done.