From: Colin Walters <walters@verbum.org>
Date: Tue, 31 Jul 2018 21:04:26 +0000 (-0400)
Subject: ostree-remount.service: RemainAfterExit=yes
X-Git-Tag: archive/raspbian/2022.1-3+rpi1~1^2~171^2^2~25
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=dcd1522969a36eb4bed7a001154342355d0539ef;p=ostree.git

ostree-remount.service: RemainAfterExit=yes

This is standard practice for units like this; e.g. it's what
`systemd-remount-fs.service` does.  I think it may be part of
or the whole cause for
https://github.com/projectatomic/rpm-ostree/issues/1471

I haven't reproduced the problem exactly but it seems to me that
if the unit starts and is GC'd, then when systemd goes to execute
a later unit it might end up restarting it.

A noticeable side effect of this is that `systemctl status ostree-remount`
exits with code `0` as expected.

Closes: #1697
Approved by: jlebon
---

diff --git a/src/boot/ostree-remount.service b/src/boot/ostree-remount.service
index 68209f96..47e1387a 100644
--- a/src/boot/ostree-remount.service
+++ b/src/boot/ostree-remount.service
@@ -31,6 +31,7 @@ Before=systemd-tmpfiles-setup.service
 
 [Service]
 Type=oneshot
+RemainAfterExit=yes
 ExecStart=/usr/lib/ostree/ostree-remount
 StandardInput=null
 StandardOutput=syslog