Can't use cronolog with server.errorlog
It appears that cronolog can only be used with the accesslog.filename.
When server.errorlog is configured to pipe to cronolog, the following occurs:
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.
Updated by Anonymous over 16 years ago
- Status changed from New to Assigned
I have written a patch for this (well, blatantly ripped off from mod_accesslog.c):
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.).
Also available in: Atom