<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - systemd logs useless "mystery" warnings to the journal - log message fails to reference the source." href="https://bugs.freedesktop.org/show_bug.cgi?id=86415#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - systemd logs useless "mystery" warnings to the journal - log message fails to reference the source." href="https://bugs.freedesktop.org/show_bug.cgi?id=86415">bug 86415</a> from <a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> Zbigniew Jedrzejewski-Szmek</a> <pre>We could do that by storing the location for each symlink (something like FragmentPath that we have for unit files). OTOH, this would be a fairly heavy price to pay for a somewhat esotiric use case. Apart from missing dependencies, and dependency cycles, I don't think we could make use of it anywhere systemd. We could use it in systemctl cat to also show the configuration done through symlinks. That last part would definitely be useful. So it's certainly worth considering.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>