Erik Christiansen <dvalin@internode.on.net> writes:
Parallel starting of services [...] will be provided, one way or another, I expect.
This is done by default on Debian 7 under sysvinit. insserv generates dependency DAGs in /etc/init.d/.depend.*, and startpar uses them to start services in parallel. But I'm sure the systemd advocates already knew that. :-)
Incidentally, if any of your posts on this thread have described a specific showstopper that you have personally experienced in systemd, or can tell us how to replicate, then I have missed it.
I'm not even using systemd and this one got me yesterday: http://bugs.debian.org/762007 1. systemd responds to "debug" in /proc/cmdline by printing SO MUCH CRAP that the system became unusable[0]. 2. kernel devs got annoyed and treat everything after " -- " specially. 3. since debian-installer also used " -- " as a separator[1], it has to be patched for 3.16+ and everyone (me) using that separator has to be retrained. Granted, this will be worked around before it hits stable, and the change in behaviour is minor. When I actually start using it, then I'm sure I can have just as much fun debugging cyclic dependencies in booting off ro NFS as I did with upstart six years ago. [0] exactly the same behaviour as upstart exhibited in 2008, incidentally. [1] to mean "arguments after this should be used during install AND after install", cf. arguments like priority=low and theme=dark, which are passed only to the installer.