Bug#884425: apcupsd start immediately after apt install

2018-03-21 Thread Thorsten Alteholz 

Hi,

I am not sure that the startup behaviour of the daemon should depend on 
the maintainer scripts executed during installation.


Wouldn't it be better to let the admin decide and configure it? In this 
case something like:


 # echo -e '#!/bin/bash\nexit 101' > /usr/sbin/policy-rc.d
 # chmod +x /usr/sbin/policy-rc.d
 # /usr/sbin/policy-rc.d
 # echo $?
 101

should do the trick.
If you want different daemons to have a different startup behaviour, you 
could evaluate the first parameter of policy-rc.d as described in [1].


  Thorsten

[1] https://people.debian.org/~hmh/invokerc.d-policyrc.d-specification.txt

Bug#884425: apcupsd start immediately after apt install

2017-12-14 Thread BetaBoy 
Package: apcupsd
Version: 3.14.14-0.3
Severity: normal

Dear Maintainer,

After apt install apcupsd, I found the daemon auto started and dumping 
connection error on console.
I don't have the chance to edit the config files first before it is running
Would it be better to leave it not running right after installation?
Since not everyone want to run it with default values

For comparsion, Fedora EPEL's apcupsd rpm will not start immediately after 
installation.

Thanks.


-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.8-3-pve (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apcupsd depends on:
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u1
ii  libgcc1  1:6.3.0-18
ii  libusb-0.1-4 2:0.1.12-30
ii  libwrap0 7.6.q-26

Versions of packages apcupsd recommends:
ii  apcupsd-doc3.14.14-0.3
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4

Versions of packages apcupsd suggests:
pn  apcupsd-cgi  
ii  udev 232-25+deb9u1

-- Configuration Files:
/etc/apcupsd/apcupsd.conf changed [not included]

-- no debconf information