You are here: Home → Documentation → How To's → How to control the size of log files

Activities: PloneEdu Day 1 Sprint report May 24, 2012; Attending Plone Symposium East 2012 at Penn State May 22, 2012; UW Oshkosh Plone confab report for Dec. 9, 2011 Dec 12, 2011; UW Oshkosh Plone confab report for Jan. 6, 2012 Dec 12, 2011; UW Oshkosh Plone confab report for Dec. 16, 2011 Dec 12, 2011; More…

Plone News: The talks submission for the Plone Conf 2012 is now open! May 14, 2012; Roadmap to Plone's current and future development published May 06, 2012; Plone to be featured at Europython 2012 May 06, 2012; World Plone Day is Wednesday, April 25th Apr 23, 2012; News from the Plone-iverse – March 2012 Apr 08, 2012; More…

How to control the size of log files

by T. Kim Nguyen — last modified Aug 17, 2010 11:29 PM

how to set up logrotate

noticed the event.log and Z2.log in client[123]/log are big - how does one set up logrotate?
2.6GB for Z2.log in client2
664 MB for event.log

you can create your own logrotate.conf and state file and set it up in cron
or make it part of the restart script I suppose

ok - good idea on the restart

i'm sure theres a zope way of doing it, there always is
yeah they say use logrotate and send zope a USR2 to get it to close the logs

http://www.zope.org/Documentation/Books/ZopeBook/2_6Edition/MaintainingZope.stx

The use of SIGUSR2 does not seem to work with ZEO clients or zeocluster installations -- only with single instances!

Help

Recent Content: Attending Plone Symposium East 2012 at Penn State May 22, 2012; PloneEdu Day 1 Sprint report May 24, 2012; PSE12 TKN How to Build a Campus Intranet.pdf May 23, 2012; Plone Symposium East 2012 Slides May 23, 2012; OSA May 17, 2012; uwosh.library.ws May 16, 2012; Unsupported schema error during buildout May 11, 2012; uwosh.librarytheme Apr 27, 2012; uwosh.timeconflictcards Apr 27, 2012; Google Apps Apr 24, 2012; More…