Recent Features
| |||||||||||||
Poettering: The Biggest MythsPoettering: The Biggest MythsPosted Feb 5, 2013 2:38 UTC (Tue) by smurf (subscriber, #17840)In reply to: Poettering: The Biggest Myths by dlang Parent article: Poettering: The Biggest Myths
> socket activation has problems with response time if it takes
> a noticable amount of time for the service to start and get to steady-state.
True. On a server, you probably don't want to use socket activation.
But socket activation is only an offshoot of systemd's "let me open all the sockets up front and hand them out to the daemons" idea. And that's useful on servers with their multiple daemons, because you now no longer need 90% of your boot dependencies, which is 90% less stuff to go wrong – esp. since some of these depend on the details in your daemons' config files.
(Log in to post comments)
Poettering: The Biggest Myths Posted Feb 5, 2013 18:55 UTC (Tue) by dgm (subscriber, #49227) [Link]
> that's useful on servers with their multiple daemons, because you now no longer need 90% of your boot dependencies
I'm a bit divided about that, exactly because of this. If you don't need them, they should not be there. I fear that this will lead to distros enabling each and every service under the sun, just because they assume it will not get activated, which may or may not be true.
Poettering: The Biggest Myths Posted Feb 6, 2013 1:37 UTC (Wed) by HelloWorld (guest, #56129) [Link]
> I fear that this will lead to distros enabling each and every service under the sun
You mean like Debian has been doing for ages?
Poettering: The Biggest Myths Posted Feb 6, 2013 12:15 UTC (Wed) by smurf (subscriber, #17840) [Link]
You misunderstand.
What I mean is that if Apache needs Mysql, you no longer need to entomb that dependency in your startup scripts.
Poettering: The Biggest Myths Posted Feb 5, 2013 18:58 UTC (Tue) by khim (subscriber, #9252) [Link] True. On a server, you probably don't want to use socket activation. Yes, you absolutely do want to use socket activation on server. It guarantees that service will be brought up if needed. You may want to use other forms of activation, too - but these are optional, if your forgot to explicitly start some service which is needed by other service - socket activation is there to bail you out. Even if you bring up all the services on server startup you still want socket activation. Without socket activation you need to order them somehow and need to think about dependencies between them, etc but with socket activation you just start them all - and that's it: socket activation will guarantee that nothing will be lost.
|
|||||||||||||