1 of 7

What are the drawbacks to using mod_log_rotate and rotatelogs.exe together?

I run a couple home dev servers on Windows 7/x64. I have been using rotatelogs.exe for my log rotation for some time now with no issues . Recently, however, I decided to try out mod_log_rotate as I read some articles that made it sound quite nice.

After setting up a couple configurations, it seems that while mod_log_rotate rotates CustomLog (access log) files, it doesn't seem to do much for the ErrorLog directive(s). Consequently, I have set up my httpd.conf to use both, albeit for separate types of logging.

My question -- are there any drawbacks or hidden pitfalls I should be aware of if I use rotatelogs.exe for my ErrorLog directive(s) and allow mod_log_rotate to handle the rest? As I understand it, mod_log_rotate takes over logging duties server-wide, so how do mod_log_rotate and rotatelogs.exe interact? Is rotatelogs.exe piped data from mod_log_rotate?

Below is the (apparently working) configuration I have in httpd.conf:

# Rotate our ErrorLogs, since mod_log_rotate doesn't seem to handle this.
ErrorLog "|bin/rotatelogs.exe -l logs/error/error.%Y-%m-%d-%H_%M_%S.log 86400"
<IfModule log_rotate_module>
# Produce a log file with at human readable extension in a directory called 'access'.
CustomLog logs/access/access_log.%Y-%m-%d-%H%M%S combined

Any thoughts, suggestions, or security/operational issues for this configuration would be appreciated.