>Number: 1419 >Category: mod_log-any >Synopsis: Logging to a pipe >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Nov 14 15:20:00 PST 1997 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.24/1.3b2 >Environment: SunOS 5.5/5.6, BSD 3.0/3.1 >Description: Piping logs to an external program actually runs the program twice. Looks like its a result of calling dup() and then closing the old stream? --- Also, for the new 1.3 with the reliable piping, it would be *great* to see some other features in this area, since so many people are piping to external programs...
I'd like to see a way to have Apache buffer a set amount of logging information before piping it out... say something we could #define so that Apache didn't keep piping out 128 bytes of information, but buffered 4-8K so our external processors can run more efficiently? >How-To-Repeat: Use a simple C program to log to and have it print to it's stdout when it start's up. >Fix: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
