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. You want services to start when you need them, meaning you always keep the amount of running daemons minimal. systemd runs sshd when someone tries to connect to it and before running sshd, it makes sure all of its dependencies are running and starts them prior to starting sshd if necessary. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51a9d283.2020...@physik.fu-berlin.de