Commits on Jul 31, 2018

1. 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
   coreos/rpm-ostree#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.

   

   cgwalters committed Jul 31, 2018
   Configuration menu

   • View commit details
   • Copy full SHA for 6bc5f3d
   • Browse repository at this point

   Copy the full SHA

   6bc5f3d View commit details

   Browse the repository at this point in the history