I've done some more investigating and identified the problem; I'm just
not sure what the solution is. The problem is that nm decides the
network is up as soon as there are no interfaces that still have work
to be done ( such as obtaining a dhcp lease ). My e1000e interface
comes up in the
To not duplicate with bug, I'm attaching my problem related to mediatomb
startup.
My 'interface' file is:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
in /etc/defaults/mediatomb I have line:
MT_INTERFACE=eth0
After boot I'm checking status of mediatomb, because it doesn't
It looks that way, yes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1453602
Title:
mediatomb starts before network comes online
Status in mediatomb package in Ubuntu:
So it looks like NM-wait-online isn't waiting long/hard enough?
** Changed in: network-manager (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Yes, it is after NetworkManager-wait-online.service and network.target.
It looks like mediatomb did wait for nm-online, yet eth0 is not yet
configured ( I inserted a ExecStartPre=ifconfig -a to see in a previous
boot ).
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded:
mediatomb is After=network-manager.online,
It should certainly be After=network-online.target, I assume that was a
typo?
are you saying that it *also* has to Wants= it?
Yes. After= is purely an ordering of units, it doesn't start one.
network-manager.target needs to be Wants= (or Requires=)
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/lib/systemd/system/NetworkManager-wait-online.service;
enabled; vendor preset: enabled)
Active: inactive (dead) since Sun 2015-05-10 22:21:06 EDT; 19h ago
Process: 1089 ExecStart=/usr/bin/nm-online -s -q
7 matches
Mail list logo
