These will not work (at least not on newer versions). Need separate instances if you want separate error logs, and I believe I got syntax error on accesslog.filename
As soon as it runs, it keeps running, no exceptions ever, kind of like a swiss clockwork.
You asked about Hiawatha a while ago, well, that’s the opposite, it just frequently hangs.
Lighty and PHP work wonderfully together, nginx may have higher throughput, but also more exceptions under high load. Lighty has lower latency than nginx and way less than Apache.
This is why Wikipedia and Youtube use Lighty (with a forged Apache header, security by obscurity). Wikipedia runs heavily on PHP and shaves off some loading time with lighty’s lower latency, and Youtube just needs lower latency to keep people from zapping too soon / often.
Piratebay, from the very beginning till this day runs on Lighty too.
Ouch, that (hangs) are no good. So far (3 days) Lighty’s been running very smoothly, and it uses less resources than OpenLiteSpeed, and it feels more responsive (haven’t benchmarked, though).
Documentation might not be too impressive (dead/outdated links etc), but it’s not that complicated either.
In my testing, it seems I have to specify port 443 sockets separately for IPv4 and IPv6(?). (And duplicate the SSL config line.)
Ah, yes, thanks! I read something on the same subject on the Lighty wiki, indicated I should gain som stats first, so I configured/added the rrd module. Not shure how often I should run the script generating the PNG’s though. Currently on */5 * * * * …