From f7c5b04f69e004912327f082be8645b65bb1ff5d Mon Sep 17 00:00:00 2001 From: Kay Sievers Date: Thu, 6 Aug 2009 16:16:26 +0200 Subject: re-enable failed event tracking It did not work for the last couple of releases. If RUN{record_failed}+="..." is given, a non-zero execution will mark the event as failed. Recorded failed events can be re-triggered with: udevadm trigger --type=failed The failed tracking _might_ be useful for things which might not be ready to be executed at early bootup, but a bit later when the needed dependencies are available. In many cases though, it indicates that something is used in a way it should not. --- udev/udev-event.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'udev/udev-event.c') diff --git a/udev/udev-event.c b/udev/udev-event.c index 5716afef7a..6a8bb44cf4 100644 --- a/udev/udev-event.c +++ b/udev/udev-event.c @@ -741,7 +741,7 @@ int udev_event_execute_run(struct udev_event *event) udev_event_apply_format(event, cmd, program, sizeof(program)); envp = udev_device_get_properties_envp(event->dev); if (util_run_program(event->udev, program, envp, NULL, 0, NULL) != 0) { - if (!udev_list_entry_get_flag(list_entry)) + if (udev_list_entry_get_flag(list_entry)) err = -1; } } -- cgit v1.2.3-54-g00ecf