On Tue, 5 Mar 2019 23:39:00 +0100 Michael Biebl <[email protected]> wrote:
> Strictly speaking, we should only need either --notify-await when > starting the daemon via s-s-d, or --wait-daemon when calling udevadm > trigger. Using both probably doesn't hurt, but isn't really necessary. correct, actually only the s-s-d --notify-await solves the issue, as it was confirmed by Bill Brelsford in the messages #134 and #258 > Since I can't reproduce the original issue myself, I wonder if > udevadm trigger --wait-daemon actually works. There was conflicting > feedback regarding this matter. udevadm --wait-daemon doesn't fix this specific issue, as it doesn't retry if the connection was refused (udevadm-trigger.c:177) > Would be cool if someone affected by this problem could try the > following: it was tested a similar configuration: udevadm trigger --type=subsystems --action=add --wait-daemon ciao! _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
