udisks2

Disk Manager

Go to file

Jonathan Lebon f651544b54 Don't trigger udev if socket is not accessible In container environments or rpm-ostree systems, scriptlets are not directly run on a host system. Thus, there's no point in asking udev to reload and retrigger: the host udev wouldn't see the new rules anyway. Let's just generalize this by checking if the udev socket even exists. If not, then we can't talk to `udevd` and we should just skip the reload & trigger bits. Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1753786	2019-10-01 10:22:52 -04:00
.gitignore	* Mon Jul 22 2019 Tomas Bzatek <tbzatek@redhat.com> - 2.8.4-1	2019-07-23 15:00:29 +02:00
sources	* Mon Jul 22 2019 Tomas Bzatek <tbzatek@redhat.com> - 2.8.4-1	2019-07-23 15:00:29 +02:00
udisks2.spec	Don't trigger udev if socket is not accessible	2019-10-01 10:22:52 -04:00

Jonathan Lebon f651544b54 Don't trigger udev if socket is not accessible

In container environments or rpm-ostree systems, scriptlets are not
directly run on a host system. Thus, there's no point in asking udev to
reload and retrigger: the host udev wouldn't see the new rules anyway.

Let's just generalize this by checking if the udev socket even exists.
If not, then we can't talk to `udevd` and we should just skip the reload
& trigger bits.

Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1753786

2019-10-01 10:22:52 -04:00

.gitignore

* Mon Jul 22 2019 Tomas Bzatek <tbzatek@redhat.com> - 2.8.4-1

2019-07-23 15:00:29 +02:00

sources

* Mon Jul 22 2019 Tomas Bzatek <tbzatek@redhat.com> - 2.8.4-1

2019-07-23 15:00:29 +02:00

udisks2.spec

Don't trigger udev if socket is not accessible

2019-10-01 10:22:52 -04:00