[systemd-bugs] [Bug 80169] RFE: please introduce more special targets for facilities like entropy, or netfilter rules

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=80169

--- Comment #6 from Christoph Anton Mitterer <calestyo at scientia.net> ---
>Well, we will not lose ourselves in trying to
>come up with way too generic hook points.
Well but isn't that just what you do with things like network.target or
network-pre.target?
network.target says about "It only indicates that the network management stack
is up after it has been reached."... okay but what does that in turn mean?
Okay you say, that it's primary purpose is for shutdown... but this whole
definition is still quite vague.

>And I am pretty sure I have no interest in adding more
>hook points for the networking mess, this is already too complex:
>http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
Agreed... it's too complex...

But you just make this worse by how you define it... and even more worse with
network-pre.target.
It again just vaguely defined "It's PRIMARY purpose is for usage with firewall
services that want to establish a firewall before any network interface is
up."... which implies "add any secondary purposes as you like".

Also the logic "Network management services hence should set
After=network-pre.target, but avoid any Wants=network-pre.target or even
Requires=network-pre.target. Services that want to be run before the network is
configured should place Before=network-pre.target and also set
Wants=network-pre.target to pull it in. This way, unless there's actually a
service that needs to be ordered before the network is up the target is not
pulled in, hence avoiding any unnecessary synchronization point." seems to me
inferior to my proposal.

No strict guidline is given... it's not immediately clear which serivces are
the ones setting up the firewall... and there's no such nice functionality to
avoid starting services if the firewall loading failed.


>And complexity starts already with dumping too many unused and weakly
>defined unit names on them. We shouldn't add all kinds of targets
>people *might* use one day.
I fully agree... but targets named so extremely generic like "network-pre" just
open the gates for this... people will just give any meaning to it as they
think it seems to fit.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140620/0c969828/attachment.html>