/etc/init/libvirt-cgconfig-wait.conf will immediately exit if cgconfig is already considered "running"; however if that's not the case, it will go into a "sleep" case which wont be interrupted even when cgconfig actually starts: AIUI, the stop statement only prevents startup, but wont kill a running task.
For instance /etc/init/rc.conf wont start /etc/init.d/rc $RUNLEVEL if reboot is called before reaching runlevel 2, but if /etc/init.d/rc is called and someone calls reboot, it's too late to kill it.
So once libvirt-bin is waiting for libvirt-cgconfig-wait which is in sleep, we're stuck in a 120s sleep and that means libvirt-bin's startup is delayed by 120s, right?
/etc/init/ libvirt- cgconfig- wait.conf will immediately exit if cgconfig is already considered "running"; however if that's not the case, it will go into a "sleep" case which wont be interrupted even when cgconfig actually starts: AIUI, the stop statement only prevents startup, but wont kill a running task.
For instance /etc/init/rc.conf wont start /etc/init.d/rc $RUNLEVEL if reboot is called before reaching runlevel 2, but if /etc/init.d/rc is called and someone calls reboot, it's too late to kill it.
So once libvirt-bin is waiting for libvirt- cgconfig- wait which is in sleep, we're stuck in a 120s sleep and that means libvirt-bin's startup is delayed by 120s, right?