On one of my test systems with the systemd NetworkManager.service enabled it is taking about 45 seconds for the loopback interface to be initialized and eth0 another about 55 seconds to become ready (both timed from first msg to ok or done).
With NetworkManager.service disabled, there is no wall clock measurable delay for loopback and eth0 to be activated.
Is this a NetworkManager issue or systemd issue? Or, something else?
TIA
Regards, OldFart
On 01/04/2011 03:32 PM, Clyde E. Kunkel wrote:
On one of my test systems with the systemd NetworkManager.service enabled it is taking about 45 seconds for the loopback interface to be initialized and eth0 another about 55 seconds to become ready (both timed from first msg to ok or done).
With NetworkManager.service disabled, there is no wall clock measurable delay for loopback and eth0 to be activated.
Is this a NetworkManager issue or systemd issue? Or, something else?
TIA
Regards, OldFart
Anyone else seeing this?
Yes, I am seeing the same thing. I am using todays updates on I686 system.
Jim
----- Original Message ----- From: "Clyde E. Kunkel" clydekunkel7734@cox.net To: "For testers of Fedora development releases" test@lists.fedoraproject.org Sent: Friday, January 07, 2011 6:14 PM Subject: Re: Is there a NetworkManager issue in Rawhide?
On 01/04/2011 03:32 PM, Clyde E. Kunkel wrote:
On one of my test systems with the systemd NetworkManager.service enabled it is taking about 45 seconds for the loopback interface to be initialized and eth0 another about 55 seconds to become ready (both timed from first msg to ok or done).
With NetworkManager.service disabled, there is no wall clock measurable delay for loopback and eth0 to be activated.
Is this a NetworkManager issue or systemd issue? Or, something else?
TIA
Regards, OldFart
Anyone else seeing this?
test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1191 / Virus Database: 1435/3364 - Release Date: 01/06/11
On 01/07/2011 08:33 PM, Jim Bevier wrote:
Yes, I am seeing the same thing. I am using todays updates on I686 system.
Jim
<snip>
I assume you are using systemd...so, where do you believe the problem lies? I looked thru the systemd and networkmanager bzs, but didn't see anything that looked relevant.
Regards, OldFart
Clyde,
I did all the updates for today and still had the same problem. I then disabled network via ntsysv, as it was enabled along with NetworkManager. The system boots without the 45 second wait for each the loopback and eth0 interfaces. Do you have network and NetworkManager both enabled at boot? That was my problem.
Jim
----- Original Message ----- From: "Clyde E. Kunkel" clydekunkel7734@cox.net To: "For testers of Fedora development releases" test@lists.fedoraproject.org Sent: Saturday, January 08, 2011 9:12 AM Subject: Re: Is there a NetworkManager issue in Rawhide?
On 01/07/2011 08:33 PM, Jim Bevier wrote:
Yes, I am seeing the same thing. I am using todays updates on I686 system.
Jim
<snip> >
I assume you are using systemd...so, where do you believe the problem lies? I looked thru the systemd and networkmanager bzs, but didn't see anything that looked relevant.
Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1191 / Virus Database: 1435/3367 - Release Date: 01/08/11
On 01/10/2011 05:33 PM, Jim Bevier wrote:
Clyde,
I did all the updates for today and still had the same problem. I then disabled network via ntsysv, as it was enabled along with NetworkManager. The system boots without the 45 second wait for each the loopback and eth0 interfaces. Do you have network and NetworkManager both enabled at boot? That was my problem.
Jim
<snip>
Yes, that was it. I wonder if this is a systemd bug? One way to find out is to bz it and find out what the gurus say?
Thanks!!
Regards, OldFart
-
Clyde E. Kunkel -
Jim Bevier