<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - please introduce more special targets for facilities like entropy, or netfilter rules" href="https://bugs.freedesktop.org/show_bug.cgi?id=80169#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - please introduce more special targets for facilities like entropy, or netfilter rules" href="https://bugs.freedesktop.org/show_bug.cgi?id=80169">bug 80169</a> from <a class="email" href="mailto:calestyo@scientia.net" title="Christoph Anton Mitterer <calestyo@scientia.net>"> Christoph Anton Mitterer</a> <pre>Perhaps one last comment... about network.target, network-pre.target vs. network-secured.target I think that "in the future" daemons should usually not depend on something like network.target... since networking get's more and more dynamic, a service like postfix would ideally discover network interfaces as they appear (and I think this is also one of the base ideas of systemd)... Truth is of course, that most services don't do this already, some perhaps never will. So in a way, one needs a "network.target"... but it should be rather made clear that this is legacy... and ideally it's defined meaning should be constrained to something like: - main network interface(s) are up, routes set - DNS for the main network is up - full stop What "main network" is should be undefined... this could be a intranet... or the internet. So while network-secured.targed, should be something that really *every* daemon or other services that does networking should Require=... network.target/network-pre.target should be rather something for legacy services and especially to be locally used (for hacks ;-) ) by sysadmins. Cheers, Chris.</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>