<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hey Mantas,<br>
    </p>
    <div class="moz-cite-prefix">On 08/07/2021 10:39, Mantas Mikulėnas
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAPWNY8XtBp+eP75eDFOONSS+mtCaNXV=JGLRwQbuRv6vnB9QpA@mail.gmail.com">
      <blockquote class="gmail_quote" style="margin:0px 0px 0px
        0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
        <div>
          <p>I am then just wondering why the issue referred to (<a
              href="https://github.com/systemd/systemd/issues/1741"
              target="_blank" moz-do-not-send="true">https://github.com/systemd/systemd/issues/1741</a>)
            is still open?<br>
            Are there still further plans to make systemd properly
            recognize that the inactive unit (pointing to a mount point
            that is used in a new and active unit) actually is
            superseeded and unmounting it makes now sense as that hits
            the new, working, active mount.<br>
          </p>
        </div>
      </blockquote>
      <div><br>
      </div>
      <div>I *think* this was supposed to improve with v249:</div>
      <div><br>
      </div>
      <div><a href="https://github.com/systemd/systemd/pull/19322"
          moz-do-not-send="true">https://github.com/systemd/systemd/pull/19322</a><br>
      </div>
      <div><a href="https://github.com/systemd/systemd/issues/19983"
          moz-do-not-send="true">https://github.com/systemd/systemd/issues/19983</a></div>
    </blockquote>
    <p>nice, thanks a bunch for the pointers!</p>
    <br>
    <blockquote type="cite"
cite="mid:CAPWNY8XtBp+eP75eDFOONSS+mtCaNXV=JGLRwQbuRv6vnB9QpA@mail.gmail.com">
      <div><br>
      </div>
      <blockquote class="gmail_quote" style="margin:0px 0px 0px
        0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
        <div>
          <p>In any case I'd suggest then is to somehow give a warning
            to the user as with changes to the systemd units:<br>
              "Warning: myfancyservice.service changed on disk. Run
            'systemctl daemon-reload' to reload units."</p>
        </div>
      </blockquote>
      <div><br>
      </div>
      <div>systemd can't make non-systemd tools (such as `mount`)
        display warnings.</div>
    </blockquote>
    <p>yeah, that's certainly true and it's much better to not need any
      warnings anyways .</p>
    <p><br>
    </p>
    <p><br>
      Regards</p>
    <p><br>
    </p>
    <p>Christian<br>
    </p>
  </body>
</html>