On Thu, 22 Nov 2012, Trent W. Buck wrote:
Uh, wtf? systemd doesn't have a monopoly on starting services in parallel. e.g. startpar is enabled by default in Debian 6.
http://manpages.debian.net/cgi-bin/man.cgi?query=startpar http://manpages.debian.net/cgi-bin/man.cgi?query=insserv
$ ls /etc/rc2.d README S02cron S03busybox-klogd S01lxc S02motd S04bootlogs S02acpid S02rsync S05rc.local S02atd S02ssh S05rmnologin S02binfmt-support S02sudo S05stop-bootlogd S02busybox-syslogd S02webfs
All those S02s start in parallel.
That sounds like a reasonable cautious approach. FreeBSD introduced rcorder few years ago (the scripts are ordered by depencies). Afterwards there was the idea of concurrency - and it caused more problems than it's worth it, especially if you have to cover the "unusual" setups as well (boots over net, network directory services, slow dynamic DHCP, to name a few) My best slowdown under Linux (back under CentOS 5.x) was using LDAP in /etc/nsswitch with files as fallback. Configured it, worked with it, all good - until next boot. Ping, ping.. no answer, one, two, three minutes. Walking over, seeing udev timing out.. for every device it configures it waits for LDAP .. which cannot be reached because there is no network yet. Amusing was the pingpong of the bug reports I found - init, udev and nsswitch - everybody reckons it was the other project's fault;-) Red Hat closed it and declared it a non-issue. Regards Peter