Hi Am 20.01.2015 um 17:30 schrieb Timothy Wegner: > Hi kp, > > You were exactly right! As you suggested I commented out the bottom > line of /etc/dhcpcd.conf: > > #background > > and then shorewall started OK.
My 0.02€ (can't use swiss francs anymore, too expensive) It cannot be the resposibility of dhcpcd to make sure shorewall starts correctly. It is the bloody duty of the init proces that starts shorewall to check for dependencies and handle errors gracefully. We did have similar issues in the past, for example using PCMCIA network cards, the same is true for ipsec without a reasonable clock (which we had). We may need a new way of detecting dependencies in the init scripts. cheers Erich
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet
------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
