Webserver tuning
WASD has a facility called “Throttle” – if there are too many concurrent requests on a resource, requests can be queued in a first-in-first-out queue, untill a given period has expired – these rquests time out with a 503 error: Server too busy.
I wanted to enable this on the PHP code because it requires rather a lolt of memory, but much to my surprise, I got 8 instances of WASD at the time. This didn’t feel too well so I reversed the changes and asked a question on the matter on the WASD mailing list.
Mark Daniel – the author – responded this was bizarre. I cannnot agree less. It is.
It’s not what should have happend, and he gave some hints to get around it, if it happens again. So I re-enabled and reloaded the mapping. Much to my surprise (and relieve) it works as expected: still one instance.
This looks better, I’ll left it running.
I also wanted to see if directory browsing could be disabled. Of course it can: in the server configuration is one entry whene directory lsiting can be enabled or disabled. Normally it will be enabled.
So I tried the effect – and the operator logs were no longer accessable, so that was not the right thing to do, for the moment. I may use a CGI-script, similar to the on ethat creates the listing of the weblogs. A good thing since that will allow access to multiple versions. Just what I need, but I still need to create it.
So I’ll keep an eye on the webserver and the system.