Feature #2489
closedAdd config option to write CGI's error output to syslog
Description
Hi,
This small patch modifies mod_cgi to send CGI's error output to syslog. Applies to 1.4.32 version.
Files
Updated by stbuehler almost 12 years ago
- Status changed from New to Wontfix
Apart from some basic issues (mixed declarations and code (C90), "simplifying" stuff that didn't need it, moving windows macro checks - i.e. stuff that should be in a separate patch with reasons why you do it, s/readed/read/, reading one char at a time is slow) your patch doesn't look bad.
But the breakage log was added for a simple reason: I didn't want to do major changes in mod_cgi. Your patch is a major change.
Also if we'd want to read stderr from cgi, we'd just forward it to lighttpds error log, and kill the breakage log.
If you need more powerful stuff (upstream) with cgi, use mod_fastcgi + fcgi-cgi - I don't think this features is worth risking to break mod_cgi.
Updated by gstrauss about 1 year ago ยท Edited
- Status changed from Wontfix to Fixed
- ASK QUESTIONS IN Forums set to No
Configure server.breakagelog
to be a piped logger. Write a short script for your custom piped logger, reading from stdin and sending to syslog.
lighttpd supports multiple server.errorlog
and multiple server.breakagelog
since lighttpd 1.4.56.
Also available in: Atom