[systemd-devel] Rate limiting socket-activating services that fail to start

[Andrey Borzenkov]

I was testing behavior when syslog.service fails to start and found
systemd taking 100% of CPU (core) time - 50% user, 50% system. See
http://marc.info/?l=opensuse&m=137127774415206&w=2

Is it possible to rate limit socket activated service? I do not see any
parameters in systemd.unit or systemd.socket.

I tried to rate limit rsyslog.service itself but it did not help. While
service itself *is* rate-limited (it is not attempted to be started
again before timeout) systemd still attempts to permanently start
service, busy looping at it.

This is openSUSE 12.3 with systemd 195 + various back ported fixes.