diff options
| author | Kay Sievers <kay.sievers@vrfy.org> | 2009-08-06 16:16:26 +0200 |
|---|---|---|
| committer | Kay Sievers <kay.sievers@vrfy.org> | 2009-08-06 16:16:26 +0200 |
| commit | f7c5b04f69e004912327f082be8645b65bb1ff5d (patch) | |
| tree | 7b3de9f37426e4b6b3204dd888950b027e235849 /udev/udev-event.c | |
| parent | 6e4025dfc8c2f6955d678b9f011c1d3b392a6e3e (diff) | |
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.
Diffstat (limited to 'udev/udev-event.c')
| -rw-r--r-- | udev/udev-event.c | 2 |
1 files changed, 1 insertions, 1 deletions
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; } } |