Couple of changes:
1. When using LogLevel 5, and there is a redirect, the code doesn't log the VirtualHost (as LogLevel=5) should. 2. More importantly (at least for us), in case of an error, pound doesn't put a very informative message in error logs. Specifically, if the error occurs after pound receives the request, and starts talking to the backend, I don't know what the original request was. This results in some number of requests (which ended up with some sort of error) not being logged. So, every time there is an error (after the client has sent the request), I'm trying logging the URI of the request & the backend. My changes are a bit crude, and I was thinking of logging messages in some sort of standard format (i.e. LogLevel=2 + error message), but didn't want to spend to much time on it.

I'm attaching the http.c file with my changes.

Albert


On 8/10/2010 4:21 PM, Joe Gooch wrote:
What changes if you don't mind me asking? :)

Joe

-----Original Message-----
From: Albert [mailto:[email protected]]
Sent: Tuesday, August 10, 2010 3:12 PM
To: [email protected]
Subject: Re: [Pound Mailing List] 2.6a testing

   We've been running that version with couple of minor changes (which
I'm hoping would be added in the next release) on couple of our
machines
for the last few weeks.  Haven't seen anything unusual.  I restarted
pound last week, and the memory consumption is inline with what we've
seen before.

Albert

On 8/10/2010 2:43 PM, Joe Gooch wrote:
Robert released 2.6a on 6/23/2010. I just thought I'd throw out there
a quick poll and see if anyone has installed or tested this version,
and if so, what have your experiences been?  I haven't seen any news go
across the list, which either means it's good news, or no one tried it.
Trying to determine which. :)
Thanks!
Joe



--
To unsubscribe send an email with subject unsubscribe to
[email protected].
Please contact [email protected] for questions.


--
To unsubscribe send an email with subject unsubscribe to
[email protected].
Please contact [email protected] for questions.
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.



--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to