On 16/11/14 13:53, Evgeni Golov wrote: > 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.
I couldn't find anything in either README file or the man page. I've never used systemd before and I'm not enjoying it. I'm not convinced the Debian packaging is ready yet for a stable release. >> 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? Dell Latitude E6540. The drive is a ST500LM000-1EJ162. Do you want any more details? >> 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? I've not tried. It's a new installation which defaulted to systemd. I'm debating whether to attempt to replace systemd with sysvinit. Thanks, Roger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
