On Tue, 31.03.15 17:10, Michal Sekletar (msekl...@redhat.com) wrote: > Users might have hard time figuring out that they need to call systemctl > reset-failed, before they are allowed to start the service again, after > service > ended up in failed state because start job rate limiting. Let's be nice and > print better error message.
Makes a lot of sense I think, but I'd prefer if we could cover more result codes? I.e. read the result value, then map it with some table to an explanation string for all currently known result codes, plus a fallback for the rest. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
