general/3460: Logresolve interprets long loglines as several loglines

[Tomas Samuelsson <jt...@cd.chalmers.se>]

>Number:         3460
>Category:       general
>Synopsis:       Logresolve interprets long loglines as several loglines
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Nov 29 10:50:00 PST 1998
>Last-Modified:
>Originator:     jts@cd.chalmers.se
>Organization:
apache
>Release:        1.3.3
>Environment:
N/A
>Description:
Logresolve only reads lines consisting of up to MAXLINE characters.
Resolving a logfile with long loglines resulted in more loglines in the
output file than in the input file. Logresolve should output the logline
unaltered except for the now resolved hostname.
>How-To-Repeat:
A logfile with a logline with more than MAXLINE characters.
>Fix:
The line length should not be a fixed length string.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]