5 ms·
while true; do NOTIFY_SOCKET=/run/systemd/notify systemd-notify ""; done Try this. As soon as you loop it, the bug is hit pretty quickly.
by SysArchitect 10y ago
while true; do NOTIFY_SOCKET=/run/systemd/notify systemd-notify ""; done
Try this. As soon as you loop it, the bug is hit pretty quickly.
- deleted 10y ago[deleted]
- nilved 10y agoI don't understand why that makes a difference if the bug is `assert(n > 0)`
- SysArchitect 10y agoI have no idea either. Race condition somewhere? It was mentioned here: https://github.com/systemd/systemd/issues/4234 https://github.com/systemd/systemd/issues/4234
- JdeBP 10y agoThere is a race in the systemd-notify mechanism that means that some notification messages get discarded if the systemd-notify process happens to complete its work and exit before systemd picks up the message. They never reach the point of the assertion that is triggered here, because systemd is unable to determine the service unit that encompasses the message sender. * http://jdebp.eu./FGA/unix-daemon-readiness-protocol-problems.html#SynchronousProtocol http://jdebp.eu./FGA/unix-daemon-readiness-protocol-problems...