Hi,
mod_slotmem cannot work on windows by design.
On windows we have two processes so the storage-grab/slotmem_grab
will always fail because the inuse flag was already set in the parent,
and since this is shared memory child will see it as used.
On unixes fork is used so the inuse is set only
On Feb 3, 2012, at 4:25 AM, Mladen Turk wrote:
Hi,
mod_slotmem cannot work on windows by design.
On windows we have two processes so the storage-grab/slotmem_grab
will always fail because the inuse flag was already set in the parent,
and since this is shared memory child will see
Under Win32, do the 2 processes know which is which?
On Feb 3, 2012, at 5:46 AM, Jim Jagielski wrote:
On Feb 3, 2012, at 4:25 AM, Mladen Turk wrote:
Hi,
mod_slotmem cannot work on windows by design.
On windows we have two processes so the storage-grab/slotmem_grab
will always fail
On 02/03/2012 11:46 AM, Jim Jagielski wrote:
On Feb 3, 2012, at 4:25 AM, Mladen Turk wrote:
Hi,
mod_slotmem cannot work on windows by design.
On windows we have two processes so the storage-grab/slotmem_grab
will always fail because the inuse flag was already set in the parent,
and since
On Feb 3, 2012, at 8:03 AM, Mladen Turk wrote:
Right, seems that's not the reason for PR52402.
Found the fix for it. The reason is the loop:
while (s) {
int i,j;
proxy_balancer *balancer;
sconf = s-module_config;
conf = (proxy_server_conf
On 02/03/2012 02:45 PM, Jim Jagielski wrote:
On Feb 3, 2012, at 8:03 AM, Mladen Turk wrote:
Right, seems that's not the reason for PR52402.
Found the fix for it. The reason is the loop:
while (s) {
int i,j;
proxy_balancer *balancer;
sconf = s-module_config;
On Fri, Feb 03, 2012 at 03:06:03PM +0100, Mladen Turk wrote:
Well actually I think that there could be multiple server_rec
for which ap_get_module_config(s-module_config,proxy_module) will
return the same proxy_server_conf.
My patch will handle those cases (the PR52402 itself)
Think I'll
On 2/3/2012 4:46 AM, Jim Jagielski wrote:
On Feb 3, 2012, at 4:25 AM, Mladen Turk wrote:
Hi,
mod_slotmem cannot work on windows by design.
On windows we have two processes so the storage-grab/slotmem_grab
will always fail because the inuse flag was already set in the parent,
and since
onsdag 30 augusti 2006 10:37 skrev Brian Akins:
With all the talk of a generic scoreboard, here's something I whipped
up that allows any other module to have some amount of memory per
worker slot. We have a different module in-house at CNN which does
something similar. This one is a little
Oden Eriksson wrote:
onsdag 30 augusti 2006 10:37 skrev Brian Akins:
With all the talk of a generic scoreboard, here's something I whipped
up that allows any other module to have some amount of memory per
worker slot. We have a different module in-house at CNN which does
something similar.
With all the talk of a generic scoreboard, here's something I whipped
up that allows any other module to have some amount of memory per
worker slot. We have a different module in-house at CNN which does
something similar. This one is a little rough around the edges, but
gives an idea of what
On Wed, 2006-08-30 at 10:37 -0400, Brian Akins wrote:
With all the talk of a generic scoreboard, here's something I whipped
up that allows any other module to have some amount of memory per
worker slot. We have a different module in-house at CNN which does
something similar. This one is a
Jean-frederic Clere wrote:
Nice stuff but I am not sure that having shared memory per slot scales
when having a lot of entries, but that makes sure that one
process/thread won't overwrite another one slot.
It scales very nicely. We run with max clients set between 16k-32k with
no issues.
Brian Akins wrote:
Jean-frederic Clere wrote:
Nice stuff but I am not sure that having shared memory per slot scales
when having a lot of entries, but that makes sure that one
process/thread won't overwrite another one slot.
It scales very nicely. We run with max clients set between
14 matches
Mail list logo
