Bug 45788 - mod_log_forensic output shouldn't be buffered when piped to filter
Summary: mod_log_forensic output shouldn't be buffered when piped to filter
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_log_forensic (show other bugs)
Version: 2.5-HEAD
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-11 22:27 UTC by Rich Wales
Modified: 2008-09-11 22:27 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rich Wales 2008-09-11 22:27:47 UTC
I need to do some network tests which require me to know exactly when any given HTTP request starts and ends. I think mod_log_forensic could give me what I need, if only there were time stamps in the forensic log data.

I tried piping the forensic log output to a filter program that prepended time stamps to each line of log data, but this didn't work because the log data was apparently being stdio-buffered as it left mod_log_forensic.  I can't think of any reason for buffering of the forensic log output as it's being piped into a filter, and I'd like to request that this buffering be turned off so that each line of log data goes immediately to the filter program.

Better yet, I'd like to propose that mod_log_forensic itself should be enhanced to include its own high-precision time stamps -- though I realize there might be resistance to doing this out of concerns for backward compatibility of the format.