[systemd-devel] Which udev action is run on boot for my device?

Marcin Kocur marcin2006 at gmail.com
Sun Oct 25 17:56:35 UTC 2020


W dniu 25.10.2020 o 18:36, Marcin Kocur pisze:
> Hello,
>
> as the topic states, I want to know which action(s) from "add", 
> "remove", "change", "move", "online", "offline", "bind", and "unbind" 
> were triggered on my device. Is there any way to check that?
>
> At the beginning of  /usr/lib/udev/rules.d/49-sane.rules there is:
>
> ACTION!="add", GOTO="libsane_rules_end"
>
> Udevadm info doesn't show libsane_matched property for my scanner.
>
> If I trigger the device manually with action "change", the variable is 
> still not there, as per the rule.
>
> But if I trigger it with "add", the variable is there and also uaccess 
> rule gets executed.
>
> So the ultimate quesiton is: what kind of trigger was executed on my 
> device on boot time?
>
Okay, it seems that "bind" is the action executed. I just edit the 
ACTION rule and restarted my PC until I found it.

Is this intended? Should I report bug to systemd or sane? The scanner is 
connected to my PC all the time.

-- 
Pozdrawiam / Greetings
Marcin Kocur █



More information about the systemd-devel mailing list