Re: [systemd-devel] systemd-udevd -any way to list triggered rules with their files etc ?

2022-10-10 Thread Lennart Poettering
On Mo, 03.10.22 02:17, Branko (bran...@avtomatika.com) wrote: > cat /etc/udev/rules.d/99-zz-network.rules: > ACTION=="add", DRIVERS=="?*", ATTR{address}=="11:22:33:44:55:66", > NAME="wlan17", OWNER="chosen_user", GROUP="chosen_group", > MODE="0666" ACTION="add" is almost always the wrong

Re: [systemd-devel] systemd-udevd -any way to list triggered rules with their files etc ?

2022-10-03 Thread Branko
On Mon, 3 Oct 2022 07:20:44 +0200 Greg KH wrote: > > Network devices do not have a group/owner/mode at all. > > > I know it does get triggered, since after replugging the WIFi stick > > I do get "wlan17" interface.But resulting created device in > > /dev/bus/usb/00x/00y gets created with

Re: [systemd-devel] systemd-udevd -any way to list triggered rules with their files etc ?

2022-10-02 Thread Greg KH
On Mon, Oct 03, 2022 at 02:17:04AM +, Branko wrote: > > cat /etc/udev/rules.d/99-zz-network.rules: > ACTION=="add", DRIVERS=="?*", ATTR{address}=="11:22:33:44:55:66", > NAME="wlan17", OWNER="chosen_user", GROUP="chosen_group", MODE="0666" Network devices do not have a group/owner/mode at

[systemd-devel] systemd-udevd -any way to list triggered rules with their files etc ?

2022-10-02 Thread Branko
I have heap of problems with udev on systemd. How is one supposed to troubleshoot rule processing ? I did do "udevadm control --log-level=debug" and tried to modify systemd-udevd.service, so that it forks-off just one chiled ( so tha the log is easier to read), but that still doesn't tell me