Le mercredi 15 juin 2011 à 09:08 +0200, Carl-Daniel Hailfinger a écrit :
Am 11.06.2011 21:53 schrieb Greg KH:
[...] Because what we have right now sucks.
Seriously, it does, it was great for the 70's and 80's when things were static, but now, it makes absolutly no sense whatsoever. Linux has been evolving to support this type of dynamic, use only what you need when you need it, type of a system for a very long time now, and this is just one piece of that progression that has been needing to change for a very long time.
So if I'm installing a web server machine with apache, it will boot quickly, but the first access to the server will take almost forever because nobody connected to port 80 before and thus apache wasn't started? Or does "use only what you need when you need it" not apply here (and if not, why)?
Looking at http://0pointer.de/blog/projects/socket-activation.html it seems that systemd socket activation adds an additional overhead of a few context switches for every single connect. How big is the performance degradation for short-lived TCP and UDP connections in that case?
Are you running apache behind xinetd ATM ? I don't think so. So I don't see why you would use socket-activation for apache server. PS : no need to cc people, just reply to mailing-list. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org