Comment # 10 on bug 987668 from Franck Bui

(In reply to James Fehlig from comment #9)
> systemd-maintainers: libvirt recently switched to directly notifying systemd
> of its readiness instead of using sd_notify
> 
> http://libvirt.org/git/?p=libvirt.git;a=commit;
> h=c0bc172383c2c955394589e5808457935ae06f1d
>

IMHO, that's just the wrong thing to do...

> This works fine on SLE12 SP2, where we've noticed the presence of
> /run/systemd/notify for $NOTIFY_SOCKET. But the file doesn't exist on SLE12
> SP1, Leap 42.1, or 13.2, which all have systemd v210. Is directly notifying
> systemd of service readiness via $NOTIFY_SOCKET supported on v210? Thanks.

Well, they decide to use their own implementation of sd_notify() so you're
basically on your own now, sorry. And it will surely break later when systemd
will decide to change any bits of the implementation of the sd_notify()
protocol.

(And of course sd_notify() is supported by systemd v210).