fmuquartet
Programmer
We have recently upgraded our apaches to 2.2.x and are experiencing a weired problem with cronolog, where it spawns multiple child process and consumes memory on apache server. After a visit to cronolog page, it appears this is a bug and there is not work around in place at the moment and these are production servers.
Is there another way of using lets say, rotatelog or any other means for time stamping a 24 hour period of the access.log (access.log_06212007)? We typically make the access log available for other teams for traffic patterns. If we try using rotatelog and there is a restart of the apaches, then we lose the 24hr period or logs, as a restart will write a new access.log.
Many Thanks,
Is there another way of using lets say, rotatelog or any other means for time stamping a 24 hour period of the access.log (access.log_06212007)? We typically make the access log available for other teams for traffic patterns. If we try using rotatelog and there is a restart of the apaches, then we lose the 24hr period or logs, as a restart will write a new access.log.
Many Thanks,