Return-Path: Delivered-To: apache-bugdb-archive@hyperreal.org Received: (qmail 2111 invoked by uid 6000); 29 Nov 1998 18:40:11 -0000 Received: (qmail 1933 invoked by uid 2001); 29 Nov 1998 18:40:07 -0000 Received: (qmail 680 invoked by uid 2012); 29 Nov 1998 18:36:41 -0000 Message-Id: <19981129183641.679.qmail@hyperreal.org> Date: 29 Nov 1998 18:36:41 -0000 From: Tomas Samuelsson Reply-To: jts@cd.chalmers.se To: apbugs@hyperreal.org X-Send-Pr-Version: 3.2 Subject: general/3459: Logresolve interprets long loglines as several loglines Sender: apache-bugdb-owner@apache.org Precedence: bulk >Number: 3459 >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:40:01 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 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! ]