On Wed, May 14, 2014 at 12:29 PM, Michal Sekletar <msekl...@redhat.com> wrote:
> On Tue, May 13, 2014 at 12:23:53AM +0200, Tom Gundersen wrote:
>> Most likely the facility needed is actual connectivity, rather than whether
>> or not the
>> network managment daemon is running.
>>
>> We also need to explicitly pull in the network-online.target, as it is not
>> active by
>> default.
>>
>> This means {systemd-networkd,NetworkManager}-wait-online.service, can be
>> enabled by default
>> as part of network-online.target, and only delay boot when some service
>> actively pulls it in.
>>
>> See: <https://bugzilla.gnome.org/show_bug.cgi?id=728965>
>>
>> Cc: Pavel Šimerda <psime...@redhat.com>
>> Cc: Michal Sekletar <msekl...@redhat.com>
>> ---
>
> I think this makes sense and with this change we can enable
> {NM,systemd-networkd}-wait-online.service by default within
> network-online.target and everything will just work. I tested it with rather
> simple test, i.e. my own daemon which does nothing but only after network is
> up,
> and I'd say it works as expected with patch applied. Note that I changed
> NM-wait-online.service on my system by hand and enabled it within
> network-online.target.
Thanks for testing! Pushed.
Tom
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
