'\n'. So I bet sed is editing the stream in place, and storing all of its
edits in memory.
LogFormat supports the '\n' character - but I still can't get sed to actually
write out to disk.
-----Original Message-
From: Joe Hammerman [mailto:jhammer...@videoegg.com]
Sen
: Re: [us...@httpd] Re: mod_log_config issue
Joe Hammerman wrote:
> Hi Dan,
>
> When the sed command is replaced with /bin/cat, logs are generated. Using a
> sed command that does nothing results in no log output; e.g.
>
> CustomLog "| /bin/sed s/// |/usr/bin/cronolog...&q
anuary 28, 2010 7:10 AM
To: users@httpd.apache.org
Subject: [us...@httpd] Re: mod_log_config issue
Joe Hammerman writes:
> If we replaced Sed with Cat, I'm a little confused as to what we would
> be catting; there's a stream coming in, right?
>
> To your second question
So perhaps someone on the users list has an alternative method for addressing
the issue we are encountering.
Our setup is that we have Amazon EC2 instances serving our web content. If we
logged the request host IP, we would have a log filled with the IP's of the
Amazon load balancers. Therefore
no logging information is generated.
-Original Message-
From: news [mailto:n...@ger.gmane.org] On Behalf Of Dan Poirier
Sent: Wednesday, January 27, 2010 12:03 PM
To: users@httpd.apache.org
Subject: [us...@httpd] Re: mod_log_config issue
Joe Hammerman writes:
> Hello Apache users list
Hello Apache users list.
We have an issue with mod_log_config; specifically we are trying to pipe log
output through Sed before it goes to Cronolog. The result is that we get no
output whatsoever.
Here is a sample of the directives we are using in our VirtualHost container:
CustomLog "| /b
