On Wed, 26.03.14 14:55, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
On 03/26/2014 01:50 PM, Kai Hendry wrote:
Thanks Michael for answering, :)
On 26 March 2014 18:59, Michael Biebl mbi...@gmail.com wrote:
2014-03-26 3:56 GMT+01:00 Kai Hendry hen...@webconverger.com:
If your
On Wed, 26.03.14 21:50, Kai Hendry (hen...@webconverger.com) wrote:
Thanks Michael for answering, :)
On 26 March 2014 18:59, Michael Biebl mbi...@gmail.com wrote:
2014-03-26 3:56 GMT+01:00 Kai Hendry hen...@webconverger.com:
If your daemon is not functional if the hardware is not
On Tue, Apr 1, 2014 at 6:45 AM, Kai Hendry hen...@webconverger.com wrote:
On 31 March 2014 09:54, Kai Hendry hen...@webconverger.com wrote:
Not sure what to try next? If I start it manually `sudo systemctl
start shkd@-dev-input-event0.service`, it starts working again. Is
On 31 March 2014 09:54, Kai Hendry hen...@webconverger.com wrote:
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
On 26 March 2014 22:55, Jóhann B. Guðmundsson johan...@gmail.com wrote:
SUBSYSTEM==input, ENV{ID_INPUT_KEYBOARD}==?*, ENV{.INPUT_CLASS}=kbd,
TAG+=systemd, ENV{SYSTEMD_WANTS}+=shkd@%p.service
Trying to teach myself how to fish here. How did you know it would
match this particular device?
$
В Sun, 30 Mar 2014 23:48:11 +0800
Kai Hendry hen...@webconverger.com пишет:
On 26 March 2014 22:55, Jóhann B. Guðmundsson johan...@gmail.com wrote:
SUBSYSTEM==input, ENV{ID_INPUT_KEYBOARD}==?*, ENV{.INPUT_CLASS}=kbd,
TAG+=systemd, ENV{SYSTEMD_WANTS}+=shkd@%p.service
...
Trying to teach
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
2014-03-26 3:56 GMT+01:00 Kai Hendry hen...@webconverger.com:
On 25 March 2014 18:01, Kai Hendry hen...@webconverger.com wrote:
Requires=dev-input-by\x2did-usb\x2d13ba_0001\x2devent\x2dkbd.device
On #systemd IRC I was recommended After=, and I think it's working as it
should!
Thanks Michael for answering, :)
On 26 March 2014 18:59, Michael Biebl mbi...@gmail.com wrote:
2014-03-26 3:56 GMT+01:00 Kai Hendry hen...@webconverger.com:
If your daemon is not functional if the hardware is not present, I'd
probably start it via a udev rule and SYSTEMD_WANTS.
Do you have an
On 03/26/2014 01:50 PM, Kai Hendry wrote:
Thanks Michael for answering, :)
On 26 March 2014 18:59, Michael Biebl mbi...@gmail.com wrote:
2014-03-26 3:56 GMT+01:00 Kai Hendry hen...@webconverger.com:
If your daemon is not functional if the hardware is not present, I'd
probably start it via a
On 2014-03-26 14:50, Kai Hendry wrote:
Thanks Michael for answering, :)
On 26 March 2014 18:59, Michael Biebl mbi...@gmail.com wrote:
2014-03-26 3:56 GMT+01:00 Kai Hendry hen...@webconverger.com:
If your daemon is not functional if the hardware is not present, I'd
probably start it via a udev
On 25 March 2014 18:01, Kai Hendry hen...@webconverger.com wrote:
Requires=dev-input-by\x2did-usb\x2d13ba_0001\x2devent\x2dkbd.device
On #systemd IRC I was recommended After=, and I think it's working as it should!
After=dev-input-by\x2did-usb\x2d13ba_0001\x2devent\x2dkbd.device
Is Requires=
12 matches
Mail list logo
