PGNd
2014-Oct-08 05:46 UTC
SW upstream & distro pkgs specify different 'WantedBy=..." targets in default unit files. Rationale?
The systemd unit files provided by my current distro's (openSUSE) SW pkgs include /shorewall*.service ... [Install] WantedBy=multi-user.target The service files in SW upstream's source contain, instead, /shorewall*.service ... [Install] WantedBy=basic.target Not sure yet what other distros are using. Given the systemd docs at http://www.freedesktop.org/software/systemd/man/systemd.special.html the reason for the different choice in the two SW unit files is unclear. Reading at [systemd-devel] [PATCH] Add a network-pre.target to avoid firewall leaks http://lists.freedesktop.org/archives/systemd-devel/2014-June/019908.html "... Before=basic.target means lots of totally unrelated units can't be > started in parallel to the firewall. ..." seems to indicate that there's a tradeoff between systemd simplicity and parallelization. Not sure if that's relevant here. What's the current rationale/preference for using WantedBy=multi-user.target vs WantedBy=basic.target ? ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk