On Sat, Feb 16, 2013 at 1:32 PM, Reindl Harald <[email protected]> wrote: > > > Am 16.02.2013 13:21, schrieb Peter Sztanojev: >> On Sat, Feb 16, 2013 at 1:12 PM, Reindl Harald <[email protected]> >> wrote: >>> >>> >>> Am 16.02.2013 13:05, schrieb Colin Guthrie: >>>> Can't you just make openvpn.service also part of network.target? Thus >>>> holding up network.target until after it's started and thus delaying the >>>> mount until that point (even when the mount is generated from fstab) >>> >>> and would by a lottery openvpn starts sucessful >>> >>> normally you sepcifiy "After=network.target" for OpenVPN >>> because it needs the whole network up to resolve IP >>> of the server and connect >> >> as if network.target means there is network connection up always > > yes, after the target >
no, by default network.target only means the network interface is up, it might not even have an IP address > but if you put a service inside network.target which needs the > network connection working at startup how do you make sure > that it always will come up clean you order NetworkManager-wait-online before network.target is one way _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
