Hi Michael,
On Tue, 04 Nov 2014, Michael Meskes wrote:
> Unfortunately I do not know much about the way systemd works, either. In
> particular I wonder how that event you generate makes it to acpid (when it is
> running) but does not trigger a start. Anyone with a hint?
Yes. The event is generated by the *kernel*, in particular the
sony-laptop module. Thus, it does not pass through the socket.
> Worst case I just remove the socket part and make it start by default as all
> the other services. Or should we have both, as ssh seems to have?
Probably some systemctl incantation is necessary? I did
systemctl enable acpid
and after that now at reboots the acpid is running, as expected.
I guess that something like this needs to be added to the
postinst (?) script.
I am not sure about how transition from sysV to systemd should
actually work. The transition should take the status of current
acpid into account ... no idea how all this should work together!
(A sad story that Debian Developers don't know anymore how to work
on some of the most essential parts of the system - shiny new world
of systemd :-(
Norbert
------------------------------------------------------------------------
PREINING, Norbert http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
