It does nothing of the sort. The amount of issues I've had with systemd and not booting due to non-deterministic ordering in CentOS 7 is absolutely insane. My

It does nothing of the sort. The amount of issues I've had with systemd and not booting due to non-deterministic ordering in CentOS 7 is absolutely insane. My CentOS 7 OSD nodes will sometimes not complete booting because it's hung somewhere in the boot process. There is no way to tell systemd to continue, Ctrl + C doesn't do anything and there is no way to get into the system because sshd is still not running. Booting it in debug mode to try and get more information makes the whole thing work. Also, when a unit file gets stuck, it goes into this waiting loop, which is a giant pain in the behind... I want to try and fix it, not wait 10+ minutes for the unit files to time out. Ctrl + C should immediately stop what it is trying to do and dump me into some sort of login shell so that I can then go and fix the issue... I've also had issues on Ubuntu 16.04 because of third party software that doesn't correctly set up it's Requires/Wants/Before/After's and then systemd will happily hang the whole boot process. Worst thing is that these issues become more and more apparent on systems with more cores/CPU's... so the 44 core, 88 thread systems we have show the issue way more than the 4 thread desktop that developers are using...