> network-online.target shouldn't be completing until all 'auto'
interfaces have link or some timeout is hit.
That already is the case -- networking.service (which is ifupdown, aka
"Started Raise network interfaces") is Before=network-online.target, and
the log proves that this works.
You only pa
Hi
The logged output is typical of tg3 a physical interface. The first
time you bring the interface up the kernel will log that the link is
down, which it is.
boot server with no interfaces configured
root@xenial64:~# ifconfig
loLink encap:Local Loopback
inet addr:127.0.0.1 M
Not sure why your link is flaky, i. e. why the link goes down (and back
up 3 seocnds later) after bringing up the interface. But that's nothing
that individual userspace packages can control, I'm afraid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
> Jun 02 16:58:02 xenial64 kernel: tg3 :02:00.0 enp2s0: Link is down
This seems odd. Is this a peculiarity of the tg3 driver or of your
environment? I don't see why anything the system does would cause tg3 to
drop the link.
--
You received this bug notification because you are a member of Ub
Hi
openntpd was just one example of the issue. I tried setting After
=network-online.target before opening this bug, it has no effect and is
why I mentioned "xenial server (dunno about desktop) doesn't seem to use
network-online.target".
ubuntu@xenial64:~$ systemctl list-dependencies network-onl
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ has
more information on this topic.
Ideally openntpd would handle networks coming and going more gracefully.
A dependency on network-online.target is only a band-aid.
--
You received this bug notification because you are a member o
> upstream systemd has network.target (network is configured)
This is *not* what network.target means. This is mostly being used for a
correct shutdown order, at bootup it has very little meaning. (see man
systemd.special(7)).
> Jun 02 16:58:02 xenial64 systemd[1]: Reached target Network.
> Jun 0
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
openntpd.service defines "After=network.target". Based on your
description, should it be "network-online.target" instead? Does that
help, or would we need to coordinate that change with some other change
we ship in
