Feature #296
Can't use cronolog with server.errorlog
| Status: | Fixed | Start: | ||
| Priority: | Low | Due date: | ||
| Assigned to: | - | % Done: | 100% |
|
| Category: | core | |||
| Target version: | 1.4.23 | |||
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.
Associated revisions
Add support for pipe logging for server.errorlog (fixes #296)
History
Updated by Anonymous over 3 years ago
- Status changed from New to Assigned
I have written a patch for this (well, blatantly ripped off from mod_accesslog.c):
http://blog.moria.org.uk/downloads/log-cronolog.diff
file, syslog and stderr logging all seem to work still, and I have this working to cronolog okay here. Works independently of whether mod_accesslog is also to cronolog (or equiv.).
-- cph
Updated by rkitover 5 months ago
- File log-cronolog3.diff added
Updated by stbuehler 3 months ago
- Assigned to deleted (
stbuehler) - Target version changed from 1.4.23 to 1.4.x
I don't see any reason to add this upstream - just use stderr and pipe it yourself.