Ticket #296 (assigned enhancement)
Can't use cronolog with server.errorlog
| Reported by: | anonymous | Owned by: | anonymous |
|---|---|---|---|
| Priority: | low | Milestone: | 1.4.20 |
| Component: | core | Version: | 1.4.x-svn |
| Severity: | minor | Keywords: | cronolog server.errorlog accesslog.filename patch |
| Cc: | Blocked By: | ||
| Need User Feedback: | no | Blocking: |
Description
It appears that cronolog can only be used with the accesslog.filename.
When server.errorlog is configured to pipe to cronolog, the following occurs:
Starting lighttpd. 2005-09-28 23:02:22: (log.c.60) opening errorlog '|/usr/local/sbin/cronolog /home/anthony/logs/domain.net-error_log.%Y%m%d' failed: No such file or directory 2005-09-28 23:02:22: (server.c.711) opening errorlog failed, dying
#> lighttpd -v lighttpd-1.4.3 - a light and fast webserver Build-Date: Sep 28 2005 01:27:03
This behavior is not consistent with accesslog.filename and should be either corrected or documented. Apache, for instance, allows one to use cronolog for both sets of logs. That is a more consistent configuration.

