I spent some time looking at the code: 1/ LOGLEVEL currently affects nc.log and cc.log correctly 2/ Adding "-l $LOGLEVEL" to eucalyptus-cloud opts (in /etc/init/eucalyptus.conf ) fixes verbosity for cloud-output.log 3/ cloud-debug.log and cloud-error.log are unaffected by this. Their verbosity is hardcoded in clc/modules/core/src/main/resources/log4j.xml.
I think we should fix (2) in an update and document what really is affected by LOGLEVEL in eucalyptus.conf ** Summary changed: - Changing LOGLEVEL in eucalyptus.conf doesn't affect log verbosity + LOGLEVEL in eucalyptus.conf doesn't affect cloud-*.log verbosity ** Changed in: eucalyptus (Ubuntu) Status: Confirmed => Triaged -- LOGLEVEL in eucalyptus.conf doesn't affect cloud-*.log verbosity https://bugs.launchpad.net/bugs/458001 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs