Mailinglist Archive: opensuse-bugs (5243 mails)

< Previous Next >
[Bug 808039] No network without networkmanager (cloned from #798348 to track the second issue)

https://bugzilla.novell.com/show_bug.cgi?id=808039

https://bugzilla.novell.com/show_bug.cgi?id=808039#c4


Marius Tomaschewski <mt@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|mt@xxxxxxxx |

--- Comment #4 from Marius Tomaschewski <mt@xxxxxxxx> 2013-03-11 12:01:48 UTC
---
(In reply to comment #3)
I think, I've seen an answer for following question already somewhere in
discussion, but I want to be sure, so I'm going to ask again.

Currently network starts links using "ip link set <dev> up" cmd. Is it problem
for systemd? E.g. that systemd is not able to restart network properly in such
case ...

I don't understand / can't follow. What do you mean exactly?
Why do you think "ip link set <dev> up" cmd could break systemd?


/etc/init.d/network [when in use] calls "ifup", which calls diverse "ip"
commands (ip link, ip addr, ip route) which are using netlink interface
to do their work and may also start other programs, e.g. dhcp client.

/etc/init.d/network redirects all direct/manual calls to systemd, which
calls the current network.service (that may be also NetworkManager).

When /etc/init.d/network is used, systemd calls its again from PID 0 and
inside of the network.service cgroup, that is all programs are started
there are running inside of this cgroup.

On 12.3, also all direct/manual calls to "ifup" are starting everything
in the network.service cgroup. Further ifup also rejects to do anything
when network.service resolves to another service, e.g. NetworkManager.


The problem from comment 2 happens IMO, because in the 2nd stage makes:

* /usr/lib/YaST2/startup/Second-Stage/S07-medium:

Y2_NETWORK_ACTIVE=0
rcnetwork start && Y2_NETWORK_ACTIVE=1

-> when network is already started before, Y2_NETWORK_ACTIVE=1 is set!

then yast2-network is started, which may stop, switch to NetworkManager
(needs recent yast2, see bug 798348 comment 43 and bug 800771) and start
the (new) service at the end.
So basically, network is still up [when nothing fails] after yast2-network.

But it gets stopped by the 2nd stage scripts:

* /usr/lib/YaST2/startup/Second-Stage/S09-cleanup

if test ! -z "$Y2_NETWORK_ACTIVE" ; then
rcnetwork stop
fi

--> stop network at the end when Y2_NETWORK_ACTIVE != ""
that is, it stops it always !!!

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
References