AW: AW: Patch to DorothyLocker

Hi!

>> The patch was wrong since thread.lock#acquire takes no keyword 
>> arguments. It just needs to read acquire(1).

>Looks like that fixed it. At least it now starts fine, doesn't barf and 
>stops fine on ctrl-c or sigkill. I commited it to CVS. Thanks.

Even though it does work now, it is horribly slow. Any idea what slows down
the system that  much? Even if I don't get that much lock messages, the
system is crawling with every access. I noticed this mostly in the
aggregator, but other pages are much slower, too. For example the shutdown
takes forever. And the system takes far too much CPU resources. I actually
kill -9 the system because the shutdown took forever.

Without -v it works as expected. So there must still be a bug in the
DorothyLocker stuff.

bye, Georg