spreadlogd question on CRLF schtuff
"Jay West" <[email protected]> Thu, 26 Sep 2002 16:21:04 -0500
| Newsgroups | gmane.comp.apache.mod-log-spread.user |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. ------=_NextPartTM-000-b41a95ab-f6c9-4f68-bbc9-18d7246325a0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0924_01C26578.B648CB20" ------=_NextPart_000_0924_01C26578.B648CB20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable We are using apache2, so we can't use mod log spread per se yet, = however, the mod log spread distribution includes an errorlog perl = script that we CAN use on apache2 via piping on the Transferlog = directive. One question comes to mind... If apache2 virtual hosts have a transferlog directive pointing to a = file, the logs are stored fine. If I change it to pipe through the perl = script mentioned above, the log files do wind up on the spreadlogd = machine, but each line (message) is missing the trailing LF so all the = lines are wrapped together as one huge line so to speak. I suspect my = log file analyzer will have fits with this.. so I want the LF or CRLF = that apache2 sends to make it to the log file. Does apache2 not put the = trailing delimiter if you use a pipe instead of a file, or is this = something the perl script from mod_log_spread is doing, or something = spreadlogd is doing? Any suggestions on where to fix this? Jay West Knights Direct ------=_NextPart_000_0924_01C26578.B648CB20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>We are using apache2, so we can't use = mod log=20 spread per se yet, however, the mod log spread distribution includes an = errorlog=20 perl script that we CAN use on apache2 via piping on the Transferlog = directive.=20 One question comes to mind...</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>If apache2 virtual hosts have a = transferlog=20 directive pointing to a file, the logs are stored fine. If I change it = to pipe=20 through the perl script mentioned above, the log files do wind up on the = spreadlogd machine, but each line (message) is missing the trailing LF = so all=20 the lines are wrapped together as one huge line so to speak. I suspect = my log=20 file analyzer will have fits with this.. so I want the LF or CRLF that = apache2=20 sends to make it to the log file. Does apache2 not put the trailing = delimiter if=20 you use a pipe instead of a file, or is this something the perl script = from=20 mod_log_spread is doing, or something spreadlogd is doing?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Any suggestions on where to fix = this?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Jay West</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Knights = Direct</FONT></DIV></BODY></HTML> ------=_NextPart_000_0924_01C26578.B648CB20-- --- [This E-mail scanned for viruses by Declude Virus] ------=_NextPartTM-000-b41a95ab-f6c9-4f68-bbc9-18d7246325a0--