On 31 March 2014 01:00, Andrey Borzenkov <arvidj...@gmail.com> wrote: > udevadm monitor --env would be more useful, it also shows device > attributes after event is processed.
Thank you Andrey! With %N and a reboot, the keyboard is working. However for interest sake, I un-plugged the USB device and re-inserted it and it doesn't work. Picture of it: http://up.dabase.com/2014-03-31/image.webp Here is the `udevadm monitor --env` log: http://sprunge.us/MFPQ I think "shkd@-dev-input-event0.service start request repeated too quickly, refusing to start." is the issue. [hendry@alarmpi ~]$ systemctl --full | grep shk shkd@-dev-input-event0.service loaded failed failed Simple HotKey Daemon shkd@sys-devices-platform-bcm2708_usb-usb1-1\x2d1-1\x2d1.2-1\x2d1.2.2-1\x2d1.2.2:1.0-input-input0.service loaded failed failed Simple HotKey Daemon shkd@sys-devices-platform-bcm2708_usb-usb1-1\x2d1-1\x2d1.2-1\x2d1.2.2-1\x2d1.2.2:1.0-input-input2.service loaded failed failed Simple HotKey Daemon system-shkd.slice loaded active active system-shkd.slice [hendry@alarmpi ~]$ systemctl status shkd@-dev-input-event0.service shkd@-dev-input-event0.service - Simple HotKey Daemon Loaded: loaded (/etc/systemd/system/shkd@.service; disabled) Active: failed (Result: start-limit) since Mon 2014-03-31 09:30:21 SGT; 5min ago Process: 443 ExecStart=/usr/local/bin/shkd %I (code=exited, status=1/FAILURE) Main PID: 443 (code=exited, status=1/FAILURE) Mar 31 09:30:21 alarmpi systemd[1]: Unit shkd@-dev-input-event0.service entered failed state. Mar 31 09:30:21 alarmpi systemd[1]: shkd@-dev-input-event0.service holdoff time over, scheduling restart. Mar 31 09:30:21 alarmpi systemd[1]: Stopping Simple HotKey Daemon... Mar 31 09:30:21 alarmpi systemd[1]: Starting Simple HotKey Daemon... Mar 31 09:30:21 alarmpi systemd[1]: shkd@-dev-input-event0.service start request repeated too quickly, refusing to start. Mar 31 09:30:21 alarmpi systemd[1]: Failed to start Simple HotKey Daemon. Mar 31 09:30:21 alarmpi systemd[1]: Unit shkd@-dev-input-event0.service entered failed state. Mar 31 09:30:25 alarmpi systemd[1]: Starting Simple HotKey Daemon... Mar 31 09:30:25 alarmpi systemd[1]: shkd@-dev-input-event0.service start request repeated too quickly, refusing to start. Mar 31 09:30:25 alarmpi systemd[1]: Failed to start Simple HotKey Daemon. Not sure what to try next? If I start it manually `sudo systemctl start shkd@-dev-input-event0.service`, it starts working again. Is http://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutSec= the right way to proceed? Not sure. Sidenote: Even though my /etc/udev/rules.d/98-shk-local.rules has ENV{SYSTEMD_WANTS}+="shkd@%N.service", how come shkd@sys-devices-platform-bcm2708_usb-usb1-1\x2d1-1\x2d1.2-1\x2d1.2.2-1\x2d1.2.2:1.0-input-input0.service & shkd@sys-devices-platform-bcm2708_usb-usb1-1\x2d1-1\x2d1.2-1\x2d1.2.2-1\x2d1.2.2:1.0-input-input2.service show up?? These are sys devices (%p) not %N ($devnode). Hoping you can guide me further. :) Kind regards, _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel