[peruser] [renton at 1gb.ru: broken chroot env]
taavi at kood.ee
Wed Sep 29 01:08:36 MDT 2010
On Wed, 29 Sep 2010 10:22:29 +0400, Alexey Vlasov <renton at 1gb.ru>
> In this example "w_peo481_108bb48e" is the only right processor name,
> the rest are unknown scraps,
> "<processor" and "u_6f04c3b0/apache" are just genious:)
Is this with rc1 or rc2?
I have only seen this kind of behavior if you gracefully restart the
server and look at the server-status at the same moment (with keepalive
enabled), then the server-status displays this corrupted child table
(probably because of the pool has been thrown away).
Can you confirm this happens after a graceful restart or randomly?
More information about the Peruser