Also just to clarify some of the above comments.
cgmanager does offer a dbus API but it does that on a private socket, it DOESN'T use the dbus system bus or dbus-daemon in any way, so there's absolutely no reason why cgmanager should ever wait for dbus to be started.
Also just to clarify some of the above comments.
cgmanager does offer a dbus API but it does that on a private socket, it DOESN'T use the dbus system bus or dbus-daemon in any way, so there's absolutely no reason why cgmanager should ever wait for dbus to be started.