Hi Roger, [ CCing Whoopie because he has more experience with the freefall code ]
On 11/15/2014 03:07 PM, Roger Lynn wrote: > After adding hdapsd to a newly installed Jessie laptop, it is not being > started at bootup, with nothing being logged. hdapsd is installed "disabled", you need to call "systemctl enable hdapsd" if you want to use it, I might have not documented that part properly, sorry. > Running "/etc/init.d/hdapsd start" starts it as expected: > Nov 15 14:01:36 brahms hdapsd[10763]: Selected interface: FREEFALL > Nov 15 14:01:36 brahms hdapsd[10763]: Uses hardware logic from /dev/freefall Cool, which HW is this? > However stopping hdapsd fails. Both shutting the laptop down or running > "/etc/init.d/hdapsd stop" results in a 90 second timeout after which the > process is killed: > Nov 15 14:06:48 brahms systemd[1]: hdapsd.service stop-sigterm timed out. > Killing. > Nov 15 14:06:48 brahms systemd[1]: hdapsd.service: main process exited, > code=killed, status=9/KILL > Nov 15 14:06:48 brahms systemd[1]: Unit hdapsd.service entered failed state. Interesting. I do not have any "freefall"-capable HW here, so I never tried the code myself. I guess there is something fishy in the "lets end now" code when running on freefall, but I have no direct clue. Does this happen with sysvinit too? Greets Evgeni -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
