Bug#779606: daemon-reexec starts plymouth-start.service service

Martin Pitt mpitt at debian.org
Mon Apr 27 14:58:00 BST 2015


Michael Biebl [2015-04-27 15:08 +0200]:
> Hm, but this patch was reverted again in
> be847e82cf95bf8eb589778df2aa2b3d1d7ae99e
> so it's likely that the final v220 won't have a fix for that.

Allegedly this commit replaces it:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=f78f265f405a6

At least systemctl daemon-reload does not trigger unit starts like
alsa-restore.service with systemd from upstream git head here.

But judging by the current mailing list responses this doesn't fully
fix it. This is still under active discussion though, so let's hope
there's something better for it.

That said, adding RemainAfterExit=true to things like
alsa-restore.service certainly sounds plausible too.

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150427/72f102ec/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list