> On Monday, October 8, 2001, at 08:16 PM, Stephen Wang wrote:
>
> > Apologies if this was answered in a previous thread:
> > From some mild testing, I've noticed that access_log entries will
be
> > made
> > twice for a particular request. For instance, if a client is
making a
> > request to moderator server [A] and then server [A] then backhand
> > requests
> > to server [B], then there will be entries in access_log files for
both
> > [A]
> > and [B].
> >
> > Is there a way to avoid this? Perhaps a mod_backhand command that
would
> > remove moderator requests from writing to the access_log? I ask
because
> > the
> > appearance of the double-entry corrupts the pageviews that I get
in my
> > subsequent stats program.
>
> The patch in that post is in all mod_backhand districutions after
> 1.1.1pre3. So, the current version 1.2.0 doesn't need any patches
> applied to do what it describes.
>
Which server keeps the log entries then? Server A the moderator, or
Server B the one that services the backhanded request?
If it is server B, is there a way, or a configuration parameter so
that the logs can be kept on server A? I had hoped to have the
backhand moderator server keep all logs, and my backhanded servers
keep no logs. (in my situation I will have an apache server
backhanding to an NT server for ASP pages only. However I would like
those pages to appear in the apache log files so I don't have to
bother with keeping log files on NT.)
Rob
P.S. The NT broadcaster is going well. Unfortunately I don't have a
lot of spare time to work on it. Only a few moments here and there.
I just added the code that will actually do the broadcasting. The
arriba calculation, and the statistics collection are all done and
working perfectly.
At the moment the broadcaster can be run as a NT IIS filter (so it
will come up and down with IIS), or as a regular program. I plan on
adding the capability for it to run as an NT service too. (maybe)
I have been playing around with setting up a new linux box to setup
backhand on it. Then I can test the broadcaster with backhand. I
hope all goes well. Guests are comming up to visit, so it will
probably be about a week before I can really work on it some more.
But it's getting there.
Someone had mentioned they did something similar in perl, but their
utility used a lot of CPU. They also mentioned they would be
interested in seeing how it would perform when written c++. Once the
application is started and things settle down with the broadcasting
code in place and it transmitting packets (I don't know if they are
transmitting right yet!) the machine buzzes along using only 2% of the
cpu for everything on the system including the broadcaster when the
machine is idle. The average queue length is 1.
Pretty decent!
Rob
>
> > Apologies if this was answered in a previous thread:
> > From some mild testing, I've noticed that access_log entries will
be
> > made
> > twice for a particular request. For instance, if a client is
making a
> > request to moderator server [A] and then server [A] then backhand
> > requests
> > to server [B], then there will be entries in access_log files for
both
> > [A]
> > and [B].
> >
> > Is there a way to avoid this? Perhaps a mod_backhand command that
would
> > remove moderator requests from writing to the access_log? I ask
because
> > the
> > appearance of the double-entry corrupts the pageviews that I get
in my
> > subsequent stats program.
>
> The patch in that post is in all mod_backhand districutions after
> 1.1.1pre3. So, the current version 1.2.0 doesn't need any patches
> applied to do what it describes.
>
Which server keeps the log entries then? Server A the moderator, or
Server B the one that services the backhanded request?
If it is server B, is there a way, or a configuration parameter so
that the logs can be kept on server A? I had hoped to have the
backhand moderator server keep all logs, and my backhanded servers
keep no logs. (in my situation I will have an apache server
backhanding to an NT server for ASP pages only. However I would like
those pages to appear in the apache log files so I don't have to
bother with keeping log files on NT.)
Rob
P.S. The NT broadcaster is going well. Unfortunately I don't have a
lot of spare time to work on it. Only a few moments here and there.
I just added the code that will actually do the broadcasting. The
arriba calculation, and the statistics collection are all done and
working perfectly.
At the moment the broadcaster can be run as a NT IIS filter (so it
will come up and down with IIS), or as a regular program. I plan on
adding the capability for it to run as an NT service too. (maybe)
I have been playing around with setting up a new linux box to setup
backhand on it. Then I can test the broadcaster with backhand. I
hope all goes well. Guests are comming up to visit, so it will
probably be about a week before I can really work on it some more.
But it's getting there.
Someone had mentioned they did something similar in perl, but their
utility used a lot of CPU. They also mentioned they would be
interested in seeing how it would perform when written c++. Once the
application is started and things settle down with the broadcasting
code in place and it transmitting packets (I don't know if they are
transmitting right yet!) the machine buzzes along using only 2% of the
cpu for everything on the system including the broadcaster when the
machine is idle. The average queue length is 1.
Pretty decent!
Rob