You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2016/08/29 13:54:45 UTC

[Bug 60063] New: Trivial enhancement to logresolve: flush output after each line

https://bz.apache.org/bugzilla/show_bug.cgi?id=60063

            Bug ID: 60063
           Summary: Trivial enhancement to logresolve: flush output after
                    each line
           Product: Apache httpd-2
           Version: 2.4.10
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: All
          Assignee: bugs@httpd.apache.org
          Reporter: vz-apache@zeitlins.org

This is a really trivial feature request: I'm using "tee apache.log |
logresolve > other.log" where the other.log file is being monitored (and
contains output from other sources than Apache) and since upgrading to 2.4,
logresolve output is buffered and doesn't appear in the file immediately (this
wasn't the case with 2.2).

I've worked around this by adding "apr_file_flush(outfile)" line right after
"apr_file_printf" in the main loop of logresolve, but it would be great to have
a command line option ("-f"?) to do it in the official version. If it could be
useful, I could submit the (trivial) patch doing it, please let me know if I
should do it.

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


[Bug 60063] Trivial enhancement to logresolve: flush output after each line

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60063

--- Comment #1 from Vadim Zeitlin <vz...@zeitlins.org> ---
As indicated by Rick Houser in a private email, a better idea for a patch would
be to only flush the output once all the available input is consumed, as this
would avoid the (possibly dramatic) slowdown in normal use.

Perhaps if it were implemented like this, it could even be the default
behaviour?

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org