Open KaiStarkk opened 1 month ago
As a workaround I have the udev rule just restarting the service when it detects add
I also encountered this problem.
But I think the problem is that somehow the TAG="usbip"
doesn't match in the remove line.
It works fine when just writing:
ACTION=="remove", RUN+="/usr/bin/systemctl --no-block stop usbip@%k.service"
Appears that udev isn't detecting removal. Suspect this is because the device gets unbound from the kernel and taken over by the usb module.
Here's an example of plug-unplug
And the corresponding journalctl result: