(This is related to bug 821723, which asked for ignoring the services' rate limit for systemctl invocations, but was closed as NOTABUG.)

Currently when "systemctl restart foo.service" fails due to the rate limit, a generic error message is printed:

  Job for foo.service failed. See 'systemctl status foo.service'
  and 'journalctl -xn' for details.

In http://lists.freedesktop.org/archives/systemd-devel/2012-September/006530.html Lennart suggested a more helpful error message should be shown:

"Starting foobar.service has been attempted too often too quickly, the
repeated start of the unit has been refused. To force a start please
invoke 'systemctl reset-failed foobar.service' followed by 'systemctl
start foobar.service' again."


Version-Release number of selected component (if applicable):
systemd-208-2.fc20.x86_64

How reproducible:
always

Steps to Reproduce:
1. for i in $(seq 1 10); do systemctl restart sshd; done
2.
3.

Actual results:
A generic error message.

Expected results:
A helpful error message that mentions the possibility of using "reset-failed".