On 10/9/2014 7:13 AM, PGNd wrote: > > > On Thu, Oct 9, 2014, at 07:03 AM, PGNd wrote: >> should be a safe approach -- for both current and future systemd versions. > > To my read, the following says we're ok with > >> Before=network.target network-pre.target >> Wants=network.target network-pre.target > > http://www.freedesktop.org/software/systemd/man/systemd.unit.html > > ... > Unit files may contain additional options on top of those listed here. If > systemd encounters an unknown option, it will write a warning log message but > continue loading the unit. > ... > > [Unit] Section Options > ... > Requires = > If one of the other units gets deactivated or its activation fails, > this unit will be deactivated. > ... > Often it is a better choice to use Wants= instead of Requires= in order > to achieve a system that is more robust when dealing with failing services. > ... > ... > Wants= > A weaker version of Requires=. Units listed in this option will be > started if the configuring unit is. However, if the listed units fail to > start or cannot be added to the transaction, this has no impact on the > validity of the transaction as a whole. This is the recommended way to hook > start-up of one unit to the start-up of another unit. > ... > ...
Please pardon the cross-post, but this issue should really be discussed on the development list rather than the user's list. Given the uncertainty surrounding this issue, in the 4.6.4 branch I have reverted yesterday's patch that uses network-pre.target and network-online.target for ordering Shorewall startup. For 4.6.4, we will go with Tuomo Soini's original patch that is included in RC1 (with a minor tweak to the Shorewall-init 'conflicts' specification). We can then implement a more comprehensive change in 4.6.5, thus allowing more time for discussion and testing. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
