https://bugzilla.novell.com/show_bug.cgi?id=870370
https://bugzilla.novell.com/show_bug.cgi?id=870370#c5
--- Comment #5 from Norman Gorlt 2014-05-03 19:31:57 UTC ---
Created an attachment (id=588593)
--> (http://bugzilla.novell.com/attachment.cgi?id=588593)
systemd-analyze.svg
I compared loaded services by systemctl recently.
Differences after boot / after ifup / after ifdown
in "manual" startmode
1. after boot
2. after ifup
3. after ifdown
loaded services:
1. network.service loaded active exited
2. network.service loaded active exited
network@enp0s4.service loaded active exited
user@0.service loaded active running
system-network.slice loaded active active
user-0.slice loaded active active
3. network.service loaded active exited
user@0.service loaded active running
system-network.slice loaded active active
user-0.slice loaded active active
Because it's not possible to connect in startmode "manual" I'm using currently
startmode "auto" and disconnect after boot if connection is not needed. :-(
Sometimes connection becomes not established automatically after boot.
That's why I looked for the loaded services.
If connection becomes not established automatically, following services fails.
snippet of systemctl output:
network.service loaded failed failed LSB: Configure network
interfaces and set up routing
network@enp0s25.service loaded failed failed ifup managed network
interface enp0s25
Strange, in this case it's possible to establish the connection via Qinternet.
Do not wonder because of the different name of interface.
It's the message of my main computer.
But it does not matters because the error exists on both machines.
Also strange, network.service needs very very long time for start.
see systemd-analyse.svg attachment
This is a start without fail of network.service !
--
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.