Am 30.07.21 um 22:26 schrieb Adrian Bunk:
On Wed, Jul 28, 2021 at 10:17:56PM +0200, Michael Biebl wrote:
Just a general remark that using Requires/After=systemd-udev-settle.service is a really bad idea. Whenever possible, you should avoid using it. Quoting from the systemd-udev-settle.service man page "Using this service is not recommended. There can be no guarantee that hardware is fully discovered at any specific time, because the kernel does hardware detection asynchronously, and certain buses and devices take a very long time to become ready, and also additional hardware may be plugged in at any time. Instead, services should subscribe to udev events and react to any new hardware as it is discovered. Services that, based on configuration, expect certain devices to appear, may warn or report failure after a timeout. This timeout should be tailored to the hardware type. Waiting for systemd-udev-settle.service usually slows boot significantly, because it means waiting for all unrelated events too."Here is what upstream did for this issue: https://github.com/tpm2-software/tpm2-abrmd/pull/755
Thanks for the reference. This is indeed much better. Another alternative would have been to start the service via SYSTEMD_WANTS https://www.freedesktop.org/software/systemd/man/systemd.device.html#SYSTEMD_WANTS=
OpenPGP_signature
Description: OpenPGP digital signature
