<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hey Silvio, <div class="moz-cite-prefix">On 07/07/2021 20:04, Silvio Knizek wrote: </div> <blockquote type="cite" cite="mid:2d1364def16a738040b2d3b8fb581d810f948f03.camel@gmx.net"> <pre class="moz-quote-pre" wrap="">after touching /etc/fstab you're supposed to run `systemctl daemon- reload` to re-trigger the generators. This is in fact a feature to announce changes in configuration files to systemd. See man:systemd.generator for more information.</pre> </blockquote> Thanks for the quick reply and the kind hint to the (right) documentation. I am then just wondering why the issue referred to (<a class="moz-txt-link-freetext" href="https://github.com/systemd/systemd/issues/1741">https://github.com/systemd/systemd/issues/1741</a>) is still open? 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. In any case I'd suggest then is to somehow give a warning to the user as with changes to the systemd units: "Warning: myfancyservice.service changed on disk. Run 'systemctl daemon-reload' to reload units." Otherwise the "reaction" of an unmount to a just successfully happend mount is still quite surprising to a user. Regards Christian <pre class="lang-sh s-code-block"><code class="hljs language-bash"> </code></pre> </body> </html>