diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-06-05 09:54:54 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-06-05 09:54:54 +0200 |
| commit | 97afc0351a96e0daa83964df33937967c75c644f (patch) | |
| tree | 4a9526207cfd01802e031eba272c4824fafa3f8b /src/boot | |
| parent | 4bea24696a6fb5cf3c9306e83ead5e9efc27239e (diff) | |
| download | systemd-97afc0351a96e0daa83964df33937967c75c644f.tar.gz systemd-97afc0351a96e0daa83964df33937967c75c644f.tar.bz2 systemd-97afc0351a96e0daa83964df33937967c75c644f.zip | |
udevadm trigger: log errors and return first failure
When udevadm trigger is called, the list of devices to trigger is always
generated through enumeration, and devices can come and go, so we should not
treat -ENOENT as a failure. But other types of failure should be logged.
It seems they were logged until baa30fbc2c04b23209d0b8fb3c86cd15ef9ea81a.
Also, return the first error. (I'm not sure if there are other failure modes
which we want to ignore. If they are, they'll need to be whitelisted like
-ENOENT.).
Diffstat (limited to 'src/boot')
0 files changed, 0 insertions, 0 deletions