<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: tmpfiles: allow multiple "w" lines for the same file, as long as they share all the same attributes (with the exception of the final argument to write)" href="https://bugs.freedesktop.org/show_bug.cgi?id=90455#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: tmpfiles: allow multiple "w" lines for the same file, as long as they share all the same attributes (with the exception of the final argument to write)" href="https://bugs.freedesktop.org/show_bug.cgi?id=90455">bug 90455</a> from <a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> Lennart Poettering</a> <pre>(In reply to Sergio Durigan Junior from <a href="show_bug.cgi?id=90455#c6">comment #6</a>) > (In reply to Lennart Poettering from <a href="show_bug.cgi?id=90455#c5">comment #5</a>) > > Well, if you have one line that sets the access mode to 0755 for a file, and > > another one which sets it to 0777, what do you do? It's not clear what > > actually should happen in that case, hence we generally report errors about > > conflicting lines. > > I am not a systemd developer, so I may be talking BS here, but in this case > it seems to me that the *.conf file should be processed line-by-line, i.e., > the order matters, so if you are setting the mode to 0755 and then to 0777, > the last one "wins". Well, currently the first one wins, plus you get a message informing you about the conflict. I think that's pretty OK already.</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>