STDOUT Logfile size in Apache Tomcat

[techieMoe]

At my work we have several production applications running on top of Apache Tomcat 6. The programs have a lot of auditing information (for billing purposes) and they can get rather large, growing to several gigabytes over the course of a few days. At present the only way to limit the size of those log files is to restart the Apache service every other day or so manually.

Is anyone more familiar with Tomcat? Is there a way to either limit the size of the log file or tell Apache to roll over the log and start a new one each day?

[Irithori]

have a look at http://cronolog.org/

At least in apache, you can pipe logs to an external program.
(I am unsure about tomcat in that regard)

Log into cronolog and cronolog takes care about creating and naming new logfiles based on date and time.
No more need to restart apache.

It looks like this:
.
.
CustomLog "| /usr/sbin/cronolog -S /var/log/apache_access.log /var/log/apache_access.log-%Y%m%d" combined

And yes it is production ready.
I am using it on about 70 machines running apache/php for one website.
That also creates a few kbyte of access logs

[elija]

Also consider logrotate