|
Home > Archive > AOL Webserver > September 2007 > Logging
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Ian Harding 2007-09-17, 7:11 pm |
| Is there any sane way to get combined logs from more than one instance
of AOLserver? I would like to have the entries interleaved with an
identifier of which instance they came from.
From what I have read it seems impossible.
These instances are on different physical servers too.
Thanks,
Ian
| |
| Tom Jackson 2007-09-18, 1:11 am |
| On Monday 17 September 2007 15:54, Ian Harding wrote:
> Is there any sane way to get combined logs from more than one instance
> of AOLserver? I would like to have the entries interleaved with an
> identifier of which instance they came from.
>
> From what I have read it seems impossible.
>
> These instances are on different physical servers too.
There are many sane ways, but none in real time. You will likely have to
combine and sort the logs. Are you talking about access logs or server logs?
Access logs could be captured with a forward proxy and avoid combining
different files.
tom jackson
| |
| Jeff Rogers 2007-09-18, 7:11 am |
| Ian Harding wrote:
> Is there any sane way to get combined logs from more than one instance
> of AOLserver? I would like to have the entries interleaved with an
> identifier of which instance they came from.
>
>
> These instances are on different physical servers too.
>
> Thanks,
>
> Ian
One way to address this issue with apache is mod_log_spread which sends
log messages over the spread group communications toolkit[1]. It
wouldn't be difficult to set up something similar for aolserver. I
don't know offhand if the tcl spread library is threadsafe (I suspect it
isn't), but it would probably be better in any case to redo it as a
ns_spread module that would share one spread connection across all
threads. Still, the api is straightforward and the implementation would
fairly simple. Once that's in place just use a filter proc to log to
the spread channel.
Another route would be to use syslog; I'm not familiar with any tcl libs
for that, but again a C implementation wouldn't be too tough.
-J
[1] http://spread.org/
| |
| Jade Rubick 2007-09-18, 1:11 pm |
| We use logresolvemerge.pl which is included with AWStats.
Jade
On 9/17/07, Jeff Rogers <dvrsn@diphi.com> wrote:
>
> Ian Harding wrote:
>
> One way to address this issue with apache is mod_log_spread which sends
> log messages over the spread group communications toolkit[1]. It
> wouldn't be difficult to set up something similar for aolserver. I
> don't know offhand if the tcl spread library is threadsafe (I suspect it
> isn't), but it would probably be better in any case to redo it as a
> ns_spread module that would share one spread connection across all
> threads. Still, the api is straightforward and the implementation would
> fairly simple. Once that's in place just use a filter proc to log to
> the spread channel.
>
> Another route would be to use syslog; I'm not familiar with any tcl libs
> for that, but again a C implementation wouldn't be too tough.
>
> -J
>
> [1] http://spread.org/
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to <
> listserv@listserv.aol.com> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> Subject: field of your email blank.
>
--
Jade Rubick
Acting Chief Information Officer
United eWay
jade.rubick@uwa.unitedway.org
tel (503)285-4963
fax (707)671-1333
www.UNITEDeWAY.org
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <listserv@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
| |
| Jeff Rogers 2007-09-18, 7:11 pm |
| Jeff Rogers wrote:
> One way to address this issue with apache is mod_log_spread which sends
> log messages over the spread group communications toolkit[1]. It
> wouldn't be difficult to set up something similar for aolserver. I
> don't know offhand if the tcl spread library is threadsafe (I suspect it
> isn't), but it would probably be better in any case to redo it as a
> ns_spread module that would share one spread connection across all
> threads. Still, the api is straightforward and the implementation would
> fairly simple. Once that's in place just use a filter proc to log to
> the spread channel.
I ripped out most of the tcl_spread module and changed it into an
AOLserver module that implements a single command with no options, to
send a message to a channel. I'd consider it proof-of-concept quality
code; there's plenty that could be done to improve it if there's interest.
http://home.diphi.com/users/jeffr/software/
-J
|
|
|
|
|