[systemd-devel] Conflicts no longer working as expected during boot in v235

[Michael Biebl]

Ok, the problem is apparently happening because spice-vdagent triggers
the start of a service via a udev rule.

In a minimal Debian buster installation, which does not exhibit the
problem, I can trigger the problem after adding the following two
files:

# cat /etc/systemd/system/sleep.service
[Unit]
Description=Sleep for 5 seconds

[Service]
Type=oneshot
ExecStart=/bin/sleep 5

ACTION=="add", SUBSYSTEM=="net", ENV{SYSTEMD_WANTS}="sleep.service"


# cat /etc/ude/rules.d/70-test.rules
ACTION=="add", SUBSYSTEM=="net", ENV{SYSTEMD_WANTS}="sleep.service"

After a reboot, now suddenly chrony and systemd-timesyncd are *both* running.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?