Wido den Hollander 7e64945b88 kvm: Logrotate should not touch agent.log (#3597) ... Logrotate should only touch security_group.log and resizevolume.log as the agent.log is already rotated by log4j inside the Agent. Having two systems trying to rotate agent.log leads to all kinds of issues like having binary (compressed) data in the middle of a plain-text log file. In addition we do not have to rotate the logs every day, only when they grow larger than 10M. On fairly idle hypervisors this should not cause those logs to rotate every day. Signed-off-by: Wido den Hollander <wido@widodh.nl>		2020-01-03 14:12:08 +01:00
..
agent.properties	agent: add host.reserved.mem.mb parameter documentation (#3016)	2018-11-12 11:40:37 +05:30
cloudstack-agent.logrotate.in	kvm: Logrotate should not touch agent.log (#3597)	2020-01-03 14:12:08 +01:00
developer.properties.template	committing Chip Childers patches fixing licensing headers	2012-06-12 12:32:58 -04:00
environment.properties.in	Rename cloud-agent-scripts to cloud-scripts	2012-09-13 16:29:01 +02:00
log4j-cloud.xml.in	agent: set log level to INFO as default for http wire (#2903)	2018-10-16 10:32:03 +05:30