On Wed, 2011-06-15 at 11:48 +0200, Kay Sievers wrote:
Le mercredi 15 juin 2011 à 09:08 +0200, Carl-Daniel Hailfinger a écrit :
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)?
Socket activation is mainly used to simplify service startup and to avoid to express any dependencies, and not about on-demand start.
The other example of socket activation is package upgrades. When pid 1 keeps the socket established, you can replace packages without ever losing any new connection. Udev on systemd-boots already works that way. You can kill the udev daemon, and the next kernel event will just start it again. It has not much to do with on-demand starting in the sense of start-it-only-when-it-is-needed. With systemd you can even replace services like syslogd with a different implementation without ever losing a single message. Services are also automatically restarted if a service crashes, without losing any new message submitted during the time the service was not available. Clients will never see connection refused. These are mostly features enterprise users asked for, and what no other init can really provide or work around. Kay -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org