[systemd-bugs] [Bug 57773] systemd needs a sockets-pre.target

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 14 16:49:17 PST 2013


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

Lennart Poettering <lennart at poettering.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|systemd needs a             |systemd needs a
                   |firewall.target             |sockets-pre.target

--- Comment #1 from Lennart Poettering <lennart at poettering.net> ---
Hmm, the firewall actually needs to be initialized before we set up the various
.socket units, so that there is no time window where the socket is bound but
the firewall not yet up. Currently there is no nice way to order a service
before all sockets are up. I have now added to the TODO list that we should
introduce "sockets-pre.target" which would be sorted before all socket units,
and before which the fw would then have to sort itself.

That also means that any firewall setup needs to happen as part of early boot.

sockets-pre.target would be ordered before basic.target, normal services are
ordered after basic.target. That means all normal services would then be run
with firewall up. sockets-pre.target would hence be a more generic
firewall.target the way you requested it.

-- 
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/20130115/5033dc66/attachment-0001.html>


More information about the systemd-bugs mailing list