Comment Re:Non-system Admin Here (Score 1) 863
Problem is, switching from bash scripts to systemD isn't going to make you go any faster. Bash scripts were designed for systems with clock speeds of single-digit megahertz. On a modern system, spawning a dozen is hardly noticeable.
It's not the script itself, it's the fact that init scripts are run sequentially. I have eight cores, there's no reason for seven of them to be sitting idle while one of the services being started shoves its thumb up its ass. Anything else that doesn't care whether the stuck service lives or dies should be able to start on its own.
Traditional init scripts can not do that.
Obviously that doesn't matter to the person who admins a cloud style infrastructure where each host (virtual or physical) has only one role and thus dependencies are basically sequential, but to anyone on an end-user machine or anyone operating a multi-role server it's very useful.
tl;dr: systemd may not be the right answer, but bash scripts are not without some major flaws which will require reducing or eliminating their influence on the boot process to resolve.