On Wednesday 02 April 2014 at 12:00:07, Umut Tezduyar Lindskog wrote: > Hi Ivan, > > On Wed, Apr 2, 2014 at 11:41 AM, Ivan Shapovalov <intelfx...@gmail.com> wrote: > > Hello all, > > > > I've noticed that systemd-networkd.service (ordered Before=network.target) > > finishes its startup before the connection is established/failed. Because > > of this, some networking daemons ordered After=network.target (like > > openvpn) are prone to failures when they attempt to connect at startup. > Please take a look at > http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/. It is > explained there what network.target actually does. > What you are expecting is a phase where interfaces up and configured. > There has been some work coming up for this, > 020d59000f86b3d98be763eaee6a2671f0427e46. > > Thanks, > Umut
Thanks for the link, got it. I think that for my usecase (a single interface) it is in fact usable, so I'll craft a wait-online unit using NM's one as a reference. Are there any pitfalls? -- Ivan Shapovalov / intelfx / > > > Is this intended, or is this a bug, or have I overlooked some piece of > > configuration? > > > > Thanks, > > -- > > Ivan Shapovalov / intelfx / > > > > (Sent from my phone. Havoc may be wreaked on the formatting.)
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
