Bug#849401: restart silently fails

On Tue, 17 Jan 2017 01:38:42 +0100 Christian Hofstaedtler wrote: > * Francesco Poli [170115 17:39]: > > Christian, have you decided which strategy should be adopted for the > > ISCONFIGURED handling? > > I'm going to set the default UPSTYPE to usb, so there will be no

Bug#849401: restart silently fails

* Francesco Poli [170115 17:39]: > Christian, have you decided which strategy should be adopted for the > ISCONFIGURED handling? I'm going to set the default UPSTYPE to usb, so there will be no activity on /dev/ttyS0 caused by the default configuration, and then

Bug#849401: restart silently fails

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 15/01/17 17:34, Francesco Poli wrote: > On Sun, 15 Jan 2017 10:28:40 +0100 Daniel Pocock wrote: > >> >> >> On 10/01/17 23:49, Christian Hofstaedtler wrote: > [...] >>> here are some test packages with a systemd service file: >>> >>>

Bug#849401: restart silently fails

On Sun, 15 Jan 2017 10:28:40 +0100 Daniel Pocock wrote: > > > On 10/01/17 23:49, Christian Hofstaedtler wrote: [...] > > here are some test packages with a systemd service > > file: > > > > https://people.debian.org/~zeha/apcupsd/ > > > > Please report back if those work for you and if the

Bug#849401: restart silently fails

On 10/01/17 23:49, Christian Hofstaedtler wrote: > Hi, > > * Daniel Pocock [170106 11:06]: >>> Is anyone able to reproduce the issue on current Debian testing? >>> >> >> How long does it take for your apcupsd daemon to shutdown? >> >> My UPS uses SNMP signalling, I wonder if

Bug#849401: restart silently fails

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/01/17 23:39, Francesco Poli wrote: > On Fri, 6 Jan 2017 11:40:20 +0100 Francesco Poli wrote: > >> On Fri, 6 Jan 2017 11:05:50 +0100 Daniel Pocock wrote: > [...] >>> My UPS uses SNMP signalling, I wonder if that makes the daemon >>> shut

Bug#849401: restart silently fails

On Fri, 13 Jan 2017 00:17:16 +0100 Christian Hofstaedtler wrote: > * Francesco Poli [170113 00:15]: > > On Wed, 11 Jan 2017 23:17:47 +0100 Christian Hofstaedtler wrote: > > > Suggestions on the actual implementation also welcome ;-) > > > > I am no systemd expert,

Bug#849401: restart silently fails

* Francesco Poli [170113 00:15]: > On Wed, 11 Jan 2017 23:17:47 +0100 Christian Hofstaedtler wrote: > > Suggestions on the actual implementation also welcome ;-) > > I am no systemd expert, but, after reading a bit of the > systemd.service(5) man page, I would think

Bug#849401: restart silently fails

On Wed, 11 Jan 2017 23:17:47 +0100 Christian Hofstaedtler wrote: > * Francesco Poli [170111 22:51]: [...] > > the apcupsd.service file seems to lack any check for the > > ISCONFIGURED variable in /etc/default/apcupsd (unlike apcupsd.init, > > which aborts whenever that

Bug#849401: restart silently fails

* Francesco Poli [170111 22:51]: > However, I glanced over the diff between > apcupsd_3.14.14-0.2.debian.tar.xz and the proposed > apcupsd_3.14.14-0.3.debian.tar.xz: the only thing that looks suspicious > is that the apcupsd.service file seems to lack any check for the

Bug#849401: restart silently fails

On Tue, 10 Jan 2017 23:49:43 +0100 Christian Hofstaedtler wrote: > Hi, Hello Christian! :-) First off, many thanks for stepping in. I really appreciate that you're proposing a longer term solution than what I was thinking about (I was planning to propose a little patch for the apcupsd.init

Bug#849401: restart silently fails

Hi, * Daniel Pocock [170106 11:06]: > > Is anyone able to reproduce the issue on current Debian testing? > > > > How long does it take for your apcupsd daemon to shutdown? > > My UPS uses SNMP signalling, I wonder if that makes the daemon shut > down more slowly. Likely.

Bug#849401: restart silently fails

On Fri, 6 Jan 2017 11:40:20 +0100 Francesco Poli wrote: > On Fri, 6 Jan 2017 11:05:50 +0100 Daniel Pocock wrote: [...] > > My UPS uses SNMP signalling, I wonder if that makes the daemon shut > > down more slowly. > > Maybe... Have you determine how long should the restart action wait between

Bug#849401: restart silently fails

On Fri, 6 Jan 2017 11:05:50 +0100 Daniel Pocock wrote: > > > On 06/01/17 11:03, Francesco Poli wrote: > > On Tue, 3 Jan 2017 22:33:53 +0100 Francesco Poli wrote: > > > >> On Mon, 26 Dec 2016 18:15:20 +0100 Daniel Pocock wrote: > >> > >> [...] > >>> apcupsd[10324]: A copy of the daemon is

Bug#849401: restart silently fails

On 06/01/17 11:03, Francesco Poli wrote: > On Tue, 3 Jan 2017 22:33:53 +0100 Francesco Poli wrote: > >> On Mon, 26 Dec 2016 18:15:20 +0100 Daniel Pocock wrote: >> >> [...] >>> apcupsd[10324]: A copy of the daemon is still running. If you >>> just stopped it, apcupsd[10324]: please wait about

Bug#849401: restart silently fails

On Tue, 3 Jan 2017 22:33:53 +0100 Francesco Poli wrote: > On Mon, 26 Dec 2016 18:15:20 +0100 Daniel Pocock wrote: > > [...] > > apcupsd[10324]: A copy of the daemon is still running. If you just > > stopped it, > > apcupsd[10324]: please wait about 5 seconds for it to shut down. > > > > > >

Bug#849401: restart silently fails

On Mon, 26 Dec 2016 18:15:20 +0100 Daniel Pocock wrote: [...] > apcupsd[10324]: A copy of the daemon is still running. If you just > stopped it, > apcupsd[10324]: please wait about 5 seconds for it to shut down. > > > Maybe the "stop" action should wait for it to really stop? Not >

Bug#849401: restart silently fails

Package: apcupsd Version: 3.14.12-1.1 Severity: serious apcupsd is correctly configured and running on my machine. I decided to restart it by typing: $ sudo systemctl restart apcupsd and the command didn't report any errors. Looking at the output of the 'ps' command, I couldn't find apcupsd