"foo knows about X, Y, and Z" doesn't mean the same thing as "foo is required for X, Y, and Z". > > replacement for these features Did GP edit their comment?

"foo knows about X, Y, and Z" doesn't mean the same thing as "foo is required for X, Y, and Z". > > replacement for these features Did GP edit their comment? The quotes and arguments you're arguing with aren't present in it. > We stopped using xinetd a loooooong time ago. If you want to use a central point of failure, that's your business. An init system that groks socket activation yields more benefits than just lazy service startup. Services which communicate over a socket can be more loosely coupled, and a service need not be a traditional "forking daemon" for dependent services to start up at the correct time (since , say, the dependency's UNIX domain socket is already created, they can all start in parallel). edit: I edited the last paragraph in 20 minutes after posting.