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/udevadm-trigger.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/udevadm-trigger.c')
| -rw-r--r-- | udev/udevadm-trigger.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/udev/udevadm-trigger.c b/udev/udevadm-trigger.c index a97feb79b3..5cd4acd6ed 100644 --- a/udev/udevadm-trigger.c +++ b/udev/udevadm-trigger.c @@ -95,7 +95,6 @@ int udevadm_trigger(struct udev *udev, int argc, char *argv[]) { "verbose", no_argument, NULL, 'v' }, { "dry-run", no_argument, NULL, 'n' }, { "type", required_argument, NULL, 't' }, - { "retry-failed", no_argument, NULL, 'F' }, { "action", required_argument, NULL, 'c' }, { "subsystem-match", required_argument, NULL, 's' }, { "subsystem-nomatch", required_argument, NULL, 'S' }, @@ -153,9 +152,6 @@ int udevadm_trigger(struct udev *udev, int argc, char *argv[]) goto exit; } break; - case 'F': - device_type = TYPE_FAILED; - break; case 'c': action = optarg; break; |