Bug#770069: Bug#769672: hdapsd: Doesn't start at boot
On 02/12/14 14:01, Roger Lynn wrote: > On 02/12/2014 13:47, Evgeni Golov wrote: >> On 11/26/2014 08:28 AM, Evgeni Golov wrote: >>> Thanks. Could you please test the following patched version: >>> https://people.debian.org/~evgeni/tmp/hdapsd_20141024-3~test1_amd64.deb >>> >>> What I do not really understand: read() should be interrupted on >>> SIGTERM/SIGUSR1, so we already should jump out of the loop!? > > As far as I remember from when I looked at the code, a signal will interrupt > the read() to call the signal handler. The signal handler sets a global > variable and returns, which means the read() continues to wait. When the > read() eventually returns the global variable is checked at the end of the > main while loop which means that the program can finish. > >> Could any one of you confirm the package as working (properly stoping) >> now, compared to the -2 version currently found in Debian? >> I'd like to get it into Jessie, but can't test properly w/o the hardware. > > Sorry, I missed your previous email. I'll try to test it in the next day or > two. It stops immediately now, although the ordering of the logs is a little strange. Here are the syslogs after starting and stopping it. Note the last line and timings: Dec 2 23:00:50 brahms hdapsd[15249]: Selected interface: FREEFALL Dec 2 23:00:50 brahms hdapsd[15249]: Uses hardware logic from /dev/freefall Dec 2 23:01:09 brahms hdapsd[15249]: Terminating hdapsd Dec 2 23:01:09 brahms systemd[1]: hdapsd.service: main process exited, code=exited, status=255/n/a Dec 2 23:01:09 brahms systemd[1]: Unit hdapsd.service entered failed state. Dec 2 23:01:09 brahms hdapsd[15249]: Tue Dec 2 23:00:50 2014: Starting hdapsd Thanks, Roger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770069: Bug#769672: hdapsd: Doesn't start at boot
On 02/12/2014 13:47, Evgeni Golov wrote: Hi, On 11/26/2014 08:28 AM, Evgeni Golov wrote: Thanks. Could you please test the following patched version: https://people.debian.org/~evgeni/tmp/hdapsd_20141024-3~test1_amd64.deb What I do not really understand: read() should be interrupted on SIGTERM/SIGUSR1, so we already should jump out of the loop!? As far as I remember from when I looked at the code, a signal will interrupt the read() to call the signal handler. The signal handler sets a global variable and returns, which means the read() continues to wait. When the read() eventually returns the global variable is checked at the end of the main while loop which means that the program can finish. Could any one of you confirm the package as working (properly stoping) now, compared to the -2 version currently found in Debian? I'd like to get it into Jessie, but can't test properly w/o the hardware. Sorry, I missed your previous email. I'll try to test it in the next day or two. Roger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770069: Bug#769672: hdapsd: Doesn't start at boot
Hi, On 11/26/2014 08:28 AM, Evgeni Golov wrote: > Thanks. Could you please test the following patched version: > https://people.debian.org/~evgeni/tmp/hdapsd_20141024-3~test1_amd64.deb > > What I do not really understand: read() should be interrupted on > SIGTERM/SIGUSR1, so we already should jump out of the loop!? Could any one of you confirm the package as working (properly stoping) now, compared to the -2 version currently found in Debian? I'd like to get it into Jessie, but can't test properly w/o the hardware. Greets Evgeni -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769672: hdapsd: Doesn't start at boot
On Mon, Nov 17, 2014 at 11:42:51PM +, Roger Lynn wrote:
> >>> strace shows:
> >>> 17912 --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=18045,
> >>> si_uid=0} ---
> >>> 17912 rt_sigaction(SIGTERM, {0x402cb0, [TERM], SA_RESTORER|SA_RESTART,
> >>> 0x7f779b2aec30}, {0x402cb0, [TERM], SA_RESTORER|SA_RESTART,
> >>> 0x7f779b2aec30}, 8) = 0
> >>> 17912 rt_sigreturn()= 0
> >>> 17912 read(3,
> >>> 17912 +++ killed by SIGKILL +++
> >
> > This is
> > ret = read(freefall_fd, &count, sizeof(count));
> > line 1249 from hdapsd.c
> >
> >>> Adding some debugging output, the SIGTERM handler is called, but the
> >>> while loop is not stopped, as the new "running" value doesn't find its
> >>> way into the main process. But here, my coding skills stop, sorry.
> >
> > read() blocks until there is something to read from /dev/freefall.
> >
> >> I started looking at this yesterday, but ran out of time. I assume the
> >> code is getting stuck in a loop or function call, which means it never
> >> returns to the main while loop in main(). This is slightly worrying: if
> >> the main loop is not running does that meant the hard disc protection is
> >> not working?
> >
> > No, it should be working, because in the case the hardware logic detects
> > a fall, the read will unblock.
>
> I can confirm that shaking the laptop while waiting for hdapsd to to
> terminate does make it unblock.
Thanks. Could you please test the following patched version:
https://people.debian.org/~evgeni/tmp/hdapsd_20141024-3~test1_amd64.deb
What I do not really understand: read() should be interrupted on
SIGTERM/SIGUSR1, so we already should jump out of the loop!?
Greets
Evgeni
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769672: hdapsd: Doesn't start at boot
On 17/11/14 17:00, Evgeni Golov wrote:
> On 11/17/2014 04:24 PM, Roger Lynn wrote:
>> On 17/11/2014 11:12, Whoopie wrote:
>>> It looks like hdapsd doesn't terminate in time, it get's KILLed after
>>> 30 seconds, see the do_stop() function in /etc/init.d/hdapsd:
>>> start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile
>>> $PIDFILE --name $NAME
>>>
>>> strace shows:
>>> 17912 --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=18045,
>>> si_uid=0} ---
>>> 17912 rt_sigaction(SIGTERM, {0x402cb0, [TERM], SA_RESTORER|SA_RESTART,
>>> 0x7f779b2aec30}, {0x402cb0, [TERM], SA_RESTORER|SA_RESTART,
>>> 0x7f779b2aec30}, 8) = 0
>>> 17912 rt_sigreturn()= 0
>>> 17912 read(3,
>>> 17912 +++ killed by SIGKILL +++
>
> This is
> ret = read(freefall_fd, &count, sizeof(count));
> line 1249 from hdapsd.c
>
>>> Adding some debugging output, the SIGTERM handler is called, but the
>>> while loop is not stopped, as the new "running" value doesn't find its
>>> way into the main process. But here, my coding skills stop, sorry.
>
> read() blocks until there is something to read from /dev/freefall.
>
>> I started looking at this yesterday, but ran out of time. I assume the
>> code is getting stuck in a loop or function call, which means it never
>> returns to the main while loop in main(). This is slightly worrying: if
>> the main loop is not running does that meant the hard disc protection is
>> not working?
>
> No, it should be working, because in the case the hardware logic detects
> a fall, the read will unblock.
I can confirm that shaking the laptop while waiting for hdapsd to to
terminate does make it unblock.
Thanks,
Roger
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769672: hdapsd: Doesn't start at boot
Hi,
On 11/17/2014 04:24 PM, Roger Lynn wrote:
> On 17/11/2014 11:12, Whoopie wrote:
>> It looks like hdapsd doesn't terminate in time, it get's KILLed after
>> 30 seconds, see the do_stop() function in /etc/init.d/hdapsd:
>> start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile
>> $PIDFILE --name $NAME
>>
>> strace shows:
>> 17912 --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=18045,
>> si_uid=0} ---
>> 17912 rt_sigaction(SIGTERM, {0x402cb0, [TERM], SA_RESTORER|SA_RESTART,
>> 0x7f779b2aec30}, {0x402cb0, [TERM], SA_RESTORER|SA_RESTART,
>> 0x7f779b2aec30}, 8) = 0
>> 17912 rt_sigreturn()= 0
>> 17912 read(3,
>> 17912 +++ killed by SIGKILL +++
This is
ret = read(freefall_fd, &count, sizeof(count));
line 1249 from hdapsd.c
>> Adding some debugging output, the SIGTERM handler is called, but the
>> while loop is not stopped, as the new "running" value doesn't find its
>> way into the main process. But here, my coding skills stop, sorry.
read() blocks until there is something to read from /dev/freefall.
> I started looking at this yesterday, but ran out of time. I assume the
> code is getting stuck in a loop or function call, which means it never
> returns to the main while loop in main(). This is slightly worrying: if
> the main loop is not running does that meant the hard disc protection is
> not working?
No, it should be working, because in the case the hardware logic detects
a fall, the read will unblock.
> Should the instructions at:
> https://www.debian.org/doc/manuals/debian-reference/ch12.en.html#_debugging_the_debian_package
> build me a package with debugging enabled?
Yes, but I do not think this is needed anymore as we have found our
problem and now just need a proper fix.
Regards
Evgeni
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769672: hdapsd: Doesn't start at boot
On 16/11/14 17:09, Evgeni Golov wrote: On 11/16/2014 06:00 PM, Evgeni Golov wrote: Right, how about this: The correct patch would be: diff --git a/debian/README.Debian b/debian/README.Debian index 97ea7cf..f914834 100644 --- a/debian/README.Debian +++ b/debian/README.Debian @@ -1,6 +1,16 @@ hdapsd for Debian - +disable hdapsd +== + +hdapsd can be disabled on boot, if you want to start it manually. + +To disable hdapsd under systemd, use systemctl disable hdapsd.service. +For inits using the init.d scripts, adjust /etc/default/hdapsd to have + START=no +in it. + hdapsd with kernels <= 2.6.27 = diff --git a/debian/rules b/debian/rules index fdbeae1..a7c6726 100755 --- a/debian/rules +++ b/debian/rules @@ -14,10 +14,3 @@ override_dh_auto_install: override_dh_auto_clean: dh_auto_clean rm -f $(CURDIR)/misc/*.service - -override_dh_systemd_enable: - # Do not enable the file by default on purpose. - # The user should enable it only after making sure the configuration is - # appropriate for his/her computer. - # This corresponds to START=no in /etc/default/hdapsd - dh_systemd_enable --no-enable That would also enable hdapsd after installation on systemd, which is what you actually want. That looks reasonable. I had found the START=yes line, which didn't help me on systemd. I can't think of any reason why you would install the package and want it to not run. The default configuration looks as if it should work for the majority of cases and I assume it's not going to do any harm if it's incorrectly configured or if the hardware doesn't exist. It's not as if it is opening network ports with security implications. 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. systemd packaging or hdapsd packaging? systemd. I am surprised at how much sysvinit configuration is apparently not implemented in systemd. And I'm struggling with the lack of configuration files with only a binary interface through systemctl. Roger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769672: hdapsd: Doesn't start at boot
On 17/11/2014 11:12, Whoopie wrote:
I can reproduce the issue:
$ sudo /etc/init.d/hdapsd start
* Starting IBM Hard Disk Active Protection System (HDAPS) daemon hdapsd
[ OK ]
real0m2.059s
user0m0.050s
sys 0m0.023s
$ time sudo /etc/init.d/hdapsd stop
* Stopping IBM Hard Disk Active Protection System (HDAPS) daemon hdapsd
[ OK ]
real0m30.079s
user0m0.083s
sys 0m0.285s
It looks like hdapsd doesn't terminate in time, it get's KILLed after 30
seconds, see the do_stop() function in /etc/init.d/hdapsd:
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE
--name $NAME
strace shows:
17912 --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=18045, si_uid=0}
---
17912 rt_sigaction(SIGTERM, {0x402cb0, [TERM], SA_RESTORER|SA_RESTART,
0x7f779b2aec30}, {0x402cb0, [TERM], SA_RESTORER|SA_RESTART, 0x7f779b2aec30}, 8)
= 0
17912 rt_sigreturn()= 0
17912 read(3,
17912 +++ killed by SIGKILL +++
Adding some debugging output, the SIGTERM handler is called, but the while loop is not
stopped, as the new "running" value doesn't find its way into the main process.
But here, my coding skills stop, sorry.
I started looking at this yesterday, but ran out of time. I assume the code
is getting stuck in a loop or function call, which means it never returns to
the main while loop in main(). This is slightly worrying: if the main loop
is not running does that meant the hard disc protection is not working?
Any signal apart from SIGTERM and SIGUSR1 is not caught and causes an
immediate exit without shutting down nicely.
Should the instructions at:
https://www.debian.org/doc/manuals/debian-reference/ch12.en.html#_debugging_the_debian_package
build me a package with debugging enabled?
Roger
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769672: hdapsd: Doesn't start at boot
Am 16.11.2014 um 14:53 schrieb Evgeni Golov:
> 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
>
>
Hi,
I can reproduce the issue:
$ sudo /etc/init.d/hdapsd start
* Starting IBM Hard Disk Active Protection System (HDAPS) daemon hdapsd
[ OK ]
real0m2.059s
user0m0.050s
sys 0m0.023s
$ time sudo /etc/init.d/hdapsd stop
* Stopping IBM Hard Disk Active Protection System (HDAPS) daemon hdapsd
[ OK ]
real0m30.079s
user0m0.083s
sys 0m0.285s
It looks like hdapsd doesn't terminate in time, it get's KILLed after 30
seconds, see the do_stop() function in /etc/init.d/hdapsd:
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE
--name $NAME
strace shows:
17912 --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=18045, si_uid=0}
---
17912 rt_sigaction(SIGTERM, {0x402cb0, [TERM], SA_RESTORER|SA_RESTART,
0x7f779b2aec30}, {0x402cb0, [TERM], SA_RESTORER|SA_RESTART, 0x7f779b2aec30}, 8)
= 0
17912 rt_sigreturn()= 0
17912 read(3,
17912 +++ killed by SIGKILL +++
Adding some debugging output, the SIGTERM handler is called, but the while loop
is not stopped, as the new "running" value doesn't find its way into the main
process. But here, my coding skills stop, sorry.
Regards,
Whoopie
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769672: hdapsd: Doesn't start at boot
On 11/16/2014 06:00 PM, Evgeni Golov wrote: > Right, how about this: The correct patch would be: diff --git a/debian/README.Debian b/debian/README.Debian index 97ea7cf..f914834 100644 --- a/debian/README.Debian +++ b/debian/README.Debian @@ -1,6 +1,16 @@ hdapsd for Debian - +disable hdapsd +== + +hdapsd can be disabled on boot, if you want to start it manually. + +To disable hdapsd under systemd, use “systemctl disable hdapsd.service”. +For inits using the init.d scripts, adjust /etc/default/hdapsd to have + START=no +in it. + hdapsd with kernels <= 2.6.27 = diff --git a/debian/rules b/debian/rules index fdbeae1..a7c6726 100755 --- a/debian/rules +++ b/debian/rules @@ -14,10 +14,3 @@ override_dh_auto_install: override_dh_auto_clean: dh_auto_clean rm -f $(CURDIR)/misc/*.service - -override_dh_systemd_enable: - # Do not enable the file by default on purpose. - # The user should enable it only after making sure the configuration is - # appropriate for his/her computer. - # This corresponds to START=no in /etc/default/hdapsd - dh_systemd_enable --no-enable That would also enable hdapsd after installation on systemd, which is what you actually want. Still not sure what makes your system not able to stop hdapsd properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769672: hdapsd: Doesn't start at boot
On 11/16/2014 05:11 PM, Roger Lynn wrote: >> 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. Right, how about this: --- a/debian/README.Debian +++ b/debian/README.Debian @@ -1,6 +1,20 @@ hdapsd for Debian - +enable hdapsd += + +hdapsd is not automatically started after installation, as you usually +want to adjust the settings for your needs (and your hardware) before +using it. + +If you really want to enable hdapsd set START=yes in /etc/defaul/hdapsd +if you are using sysvinit (or any other init using init.d scripts). + +If you are using systemd, use “systemctl enable thinkfan.service” — as is +customary with systemd, hdapsd.service ignores /etc/default/hdapsd. + + hdapsd with kernels <= 2.6.27 = Would that help? But reading the code, it seems it actually is enabled by default on sysvinit. Meh. I'll fix this. > 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. systemd packaging or hdapsd packaging? > Dell Latitude E6540. The drive is a ST500LM000-1EJ162. Do you want any more > details? Nah, the DELL part was interesting, thanks. Greets Evgeni -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769672: hdapsd: Doesn't start at boot
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
Bug#769672: hdapsd: Doesn't start at boot
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
Bug#769672: hdapsd: Doesn't start at boot
Package: hdapsd Version: 1:20141024-1 Severity: important Hi, After adding hdapsd to a newly installed Jessie laptop, it is not being started at bootup, with nothing being logged. 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 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. Regards, Roger -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages hdapsd depends on: ii init-system-helpers 1.21 ii libc62.19-13 ii libconfig9 1.4.9-2 Versions of packages hdapsd recommends: pn tp-smapi-dkms | tp-smapi-source hdapsd suggests no packages. -- Configuration Files: /etc/hdapsd.conf changed: device="sda"; adaptive=true; syslog=true; -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
