[Pkg-acpi-devel] Bug#766991: Bug#766991: acpid: does not process events

[Michael Biebl]

Am 05.11.2014 um 13:02 schrieb Norbert Preining:
> On Wed, 05 Nov 2014, Michael Biebl wrote:
>> A "systemctl enable systemd.service" will hook up acpid.service in
> 
> acpid.service I guess. Yes, but how is that to be incorporated into
> the dpkg scripts?
> 
> Does systemd provide any mechanism for that? When and how should
> the script be run? On every postinst?

The proposed mechanism to enable systemd unit in mintainer script is the
use of dh_systemd. It is possible to enable both, .service *and* socket
unit. Atm, acpid explicitly does *not* enable the .service unit but only
the .socket unit:

override_dh_systemd_enable:
       dh_systemd_enable --no-enable debian/acpid.service
       dh_systemd_enable debian/acpid.socket


> And, in the end *why* was it disabled at all?

That's a decision that's up to the maintainer.
Under systemd, there are multiple triggers, how a service can be started

a/ during boot by being pulled in via one of the standard targets like
multi-user.target

b/ via socket activation, by a .socket unit

c/ via hardware events (triggered via udev rules, by tagging a device
and setting ENV{SYSTEMD_WANTS}+="foo.service")

d/ via D-Bus service activation, by a dbus system service file.

e/ timer events, by a .timer unit


The maintainer can decide, which one of those is the most suitable for a
given service. It can also be a combination of multiple triggers.




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-acpi-devel/attachments/20141105/c5a0de92/attachment.sig>