On 06/01/2013 12:24 PM, Vincent Bernat wrote:
I don't know how systemd behaves in this way (so this is not something
to hold against upstart), but there are so many daemons that need to be
started after the network has been configured that it should be easy to
do this. For example, most daemons binding to a specific address needs
to be started after the address has been configured.
Which is exactly the very one design decision which is wrong in
upstart. Starting any service as soon as all its dependencies are
fulfilled, is putting the dependency chain upside down and doesn't
make any sense. There is no point to start a daemon unless you actually
need it.