24.01.2018 17:13, Lennart Poettering пишет: > On Mi, 24.01.18 14:51, Thomas Blume (thomas.bl...@suse.com) wrote: > >> Would this be an acceptable approach? > > Since a long time there has been a proper API for this: just take a > BSD file lock on the device node and udev won't bother with the > device anymore. As soon as you close the device fully (and thus also > lost all locks), udev will notice and then reprobe it again. >
How exactly is udev relevant here? This discussion has nothing to do with udev. > It's a bit underdocumented, but it's the right way, doesn't leave > artifacts in the system around and uses the appropriate OS primitives > for what it needs to do. > > If you need this in shell, then I figure util-linux' flock tool should > be something you can make work, as it appears to be a command line > wrapper around BSD file locks. > > Lennart > _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel