Greg Ames wrote:
> The worker_score is 208 bytes now on my Linux box.
s/208/204/
Greg
Stas Bekman wrote:
> So there are two different issues here:
>
> 1. patching the scoreboard to collect and store this extra info
>
> 2. patching mod_status to use this extra info
true
> since mod_status in the extended mode is already doing a lot of work,
> how much of an extra overhead will
Greg Ames wrote:
> Jim Jagielski wrote:
>
>
>>Well, it's kind of easy (and dangerous) to shove too much info into
>>the scoreboard, and cause some nasty overhead... That's the reason why
>>I put some things in the "extended status" area, so that we always
>>have the important stuff available, an
Jim Jagielski wrote:
> Well, it's kind of easy (and dangerous) to shove too much info into
> the scoreboard, and cause some nasty overhead... That's the reason why
> I put some things in the "extended status" area, so that we always
> have the important stuff available, and the extra stuff only w
Stas Bekman wrote:
>
> When you look at the output of mod_status (or Apache::VMonitor, the perl
> brother of mod_status) you cannot tell one port based vhost from
> another. Users ask me to present this info in Apache::VMonitor, because
> they want to tell one vhost from another in the output,
Jim Jagielski wrote:
> At 10:28 AM +0800 3/27/02, Stas Bekman wrote:
>
>>Is there anything wrong with this patch? Thanks.
>>
>
>
> Nothing that I can see... I just don't see the need. We assume that
> knowledge of the virtual host implies knowledge of the IP address
> and port. We don't place t
At 10:28 AM +0800 3/27/02, Stas Bekman wrote:
>Is there anything wrong with this patch? Thanks.
>
Nothing that I can see... I just don't see the need. We assume that
knowledge of the virtual host implies knowledge of the IP address
and port. We don't place the IP address of IP-based vhosts in the
Is there anything wrong with this patch? Thanks.
Original Message
Subject: [PATCH scoreboard] adding port entry
Date: Fri, 15 Mar 2002 11:58:31 +0800 (SGT)
From: Stas Bekman <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
When running port based vhosts we
