On Mon, May 04, 2015 at 12:48:46PM -0700, stan wrote: > Those were interesting reads. It seems the infrastructure is in place > to deal with the problem of service failure, but operational inertia is > slowing adoption. In other words, just a normal human system. :-) > The one thing I didn't see addressed was the comment requesting some > notification if a service became a chronic (ab)user of the restart > feature, so remedial action could be taken or requested.
Well, it's logged.... but, yeah. In general, we don't have a standard, integrated monitoring/alerting service for Fedora, except for desktop notifications, which aren't ideal for many cases. (Like, basically anything but a single-user desktop.) Working on fixing this would be an interesting project — maybe under Fedora Server... > It should be a simple matter for the OP to put the recommended > Restart=on-failure command into the service file under the [Service] > section for the failing services and see what happens. Yep. And note, by the way, that you shouldn't edit the files in /usr/lib/systemd/system/ — instead, create new ones in /etc/systemd/system/ with the same name. These will be merged, with values from /etc taking precedence. (And in recent systemd, you can use `systemctl cat` to show the merged files, or `systemctl edit` as a handy way to call your prefered editor to edit the config snippets.) -- Matthew Miller <mat...@fedoraproject.org> Fedora Project Leader -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
