On Wed, 2015-04-15 at 21:07 +0200, Michael Stapelberg wrote:
> > I’ve added the systemd service files manually on my qnaps
> before I
> > contributed them upstream, hence I never ran into this
> issue.
>
> What did you do manually? Does it match what I describe above?
>
>
> Yes, I think so.
When I install the resulting package I get:
Apr 15 19:43:26 qnap systemd[1]: Expecting device
dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device...
Apr 15 19:44:56 qnap systemd[1]: Job
dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device/start timed out.
Apr 15 19:44:56 qnap systemd[1]: Timed out waiting for device
dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device.
Apr 15 19:44:56 qnap systemd[1]: Dependency failed for qcontrold.
and the same seems to have happened on reboot too judging from:
# systemctl | grep -E qcontrol\|gpio
dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device
loaded inactive dead start
dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device
qcontrol.service
loaded activating start start qcontrol
qcontrold.service
loaded inactive dead start qcontrold
qcontrold.socket
loaded active running qcontrold.socket
# ls -l /dev/input/by-path/platform-gpio-keys-event
lrwxrwxrwx 1 root root 9 Apr 15 21:03
/dev/input/by-path/platform-gpio-keys-event -> ../event0
I suppose you never saw this?
I was wondering if perhaps because the device was a by-name symlink and
not a real device?
Or does the device need tagging as described in
http://www.freedesktop.org/software/systemd/man/systemd.device.html ?
Ian.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
