Remember lastest stable code is most bug free fixed refined code.
If you feel like that, just run OpenBSD -current: you get the latest
code, and if it's good enough for the developers it's good enough for
production, right? (Often, it is. Don't even try to update during
hackathons, though.)
Joachim
> No you are wrong nothing breaks.
I have used Arch Linux. Things broke on upgrade. Though to be fair by
"broke" I really mean "required manual intervention"; and it was no
different on Debian unstable.
> Remember lastest stable code is most bug free fixed refined code.
Sure, the latest code fixes bugs. It also introduces new bugs. I'm of
the "better the devil you know" philosophy.
In archlinux each pacakge is on its own. Only latest stable binary is available unless you use AUR. The kernel is like another package.
Not really, I think. Note that Apache has a setting (MaxProcesses
or something) that would need to be configured alongside the process
limit.
You'll probably find messages like 'myhttpd[12345]: cannot spawn
process: resource temporarily unavailable' in syslog when you hit the
limit.
Joachim
kqueue works well on OpenBSD.
Just try the defaults and test with some tool (I have the impression
that people like httperf, but I have no opinion myself. It, and many
similar tools, is available from ports.) You'll find out soon enough.
Joachim