On 9/22/06, Jonathan <[EMAIL PROTECTED]> wrote:
composing the info i need to log under mp is trivial
i'm a bit uneasy about actually logging to a file though-- it looks
like under a prefork model ( i need 2+ servers to handle this ), i'd
need to lock / open / write / close
On Sep 22, 2006, at 1:35 PM, Drew Wilson wrote:
Have you looked at pgLOGd? Or its successor, dbWebLog?
Both of these claim to offer low-overhead robust logging.
yeah. no dice.
the problem isn't about the overhead on apache-- its about the
overhead of the database. i believe pgLogD used
Have you looked at pgLOGd? Or its successor, dbWebLog?
Both of these claim to offer low-overhead robust logging.
Drew
On Sep 22, 2006, at 7:52 AM, Jonathan Vanasco wrote:
On Sep 22, 2006, at 6:33 AM, Sean Davis wrote:
You can create a simple logger under mod_perl that logs to a
database d
On Fri, 22 Sep 2006 03:38:52 -0700
"Philip M. Gollucci" <[EMAIL PROTECTED]> wrote:
> Sean Davis wrote:
> >>> i not need to log some basic request info ( comparable to what is
> >>> in the access log ) , along with the value of a certain cookie if
> >>> it exists- for later parsing ( faster than to
On Sep 22, 2006, at 6:33 AM, Sean Davis wrote:
You can create a simple logger under mod_perl that logs to a
database directly
using DBI. You would, of course, want to benchmark anything like
this, but
it isn't hard to code one.
No DBI. This is a high traffic server. I can't handle the
Sean Davis wrote:
>>> i not need to log some basic request info ( comparable to what is in
>>> the access log ) , along with the value of a certain cookie if it
>>> exists- for later parsing ( faster than tossing into a db )
mod_log_sql (written in C) works in both httpd 1.x and 2.x.
Its been "prof
f it
> > exists- for later parsing ( faster than tossing into a db )
> >
> > composing the info i need to log under mp is trivial
> >
> > i'm a bit uneasy about actually logging to a file though-- it looks
> > like under a prefork model ( i need 2+ server
need to change that.
>
> i not need to log some basic request info ( comparable to what is in
> the access log ) , along with the value of a certain cookie if it
> exists- for later parsing ( faster than tossing into a db )
>
> composing the info i need to log under mp is trivial
>
ivial
i'm a bit uneasy about actually logging to a file though-- it looks
like under a prefork model ( i need 2+ servers to handle this ), i'd
need to lock / open / write / close / unlock the log file per request
does anyone know of a facility that will let me just log
straightfor
