Re: Bug#736258: acpid won't stop, won't upgrade (systemd) - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736258
Jonathan de Boyne Pollard <j.deboynepollard-newsgroups@ntlworld.com>
writes:
> And bugs #734766 and #734848 tell one the answer, which is that in order
> to preserve its existing conceptual model that there is just the one
> thing (named simply "acpid") invoke-rc.d should pull out the "socket"
> from the "service" by looking for a "TriggeredBy=" relationship in the
> output of "systemctl show", and operate upon both things together,
> whenever it finds a socket-activated service. There's even an attempt
> at a patch that does that.
This isn't a very attractive solution to the problem, though, since it
undermines one of the nice features of socket activation: queuing messages
received on the socket until the service can be restarted so that no
messages on the socket are lost.
I think a better solution *for upgrades* (removal is another matter, of
course) would be to leave the socket enabled but disable socket activation
for the service and then stop the service. Then, when the service has
been upgraded, re-enable socket activation and start the service if
desired.
I'm not sure if there's a way to do this currently from the command line,
but it seems like the right thing to do to me. If it's not easy to do,
maybe we should talk to systemd upstream about making it easier?
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: