Am 18.12.19 um 17:58 schrieb Joshua:
> systemd gets stuck in boot waiting for eth0 to start.
>
> /etc/network/interfaces looks like:
>
> source /etc/network/interfaces.d/*
> auto lo
> iface lo inet loopback
> iface eth0 inet dhcp
>
> /etc/rc.local looks like:
> #!/bin/sh
> dhclient eth0 &
>
>
I suspect it might be confusing since I filed two different eth0-related bugs.
In this particular instance, the DHCP server was live, and I could
have omitted the & from the line in rc.local and it would have come up
only a couple of seconds slower.
On Sun, Apr 26, 2020 at 01:09:06PM -0700, Joshua Hudson wrote:
> I suspect it might be confusing since I filed two different eth0-related bugs.
>
> In this particular instance, the DHCP server was live, and I could
> have omitted the & from the line in rc.local and it would have come up
> only a
I never had both at the same time. I toggled of auto eth0 when I put
the line into /etc/rc.local.
> If so, what happens if you just disable rc.local?
No network connection, and "auto eth0" causes 5 mins delay at boot.
On 4/26/20, Guus Sliepen wrote:
> On Sun, Apr 26, 2020 at 01:09:06PM -0700, J
Control: reassign -1 ifupdown
Am 18.12.19 um 17:58 schrieb Joshua:
> Package: systemd
> Version: 241-7~deb10u2
> Severity: important
>
> Dear Maintainer,
>
> systemd gets stuck in boot waiting for eth0 to start.
>
> (Yes it is eth0. The assumptions in predictable network interface
> names aren'
Forgive me if I'm not quite so sure, because this is the second time
I've had an undiagnosable problem where systemd appeared to be waiting
for something to start that was already started.
On my home system I had to roll back systemd altogether because it
would hang for many minutes on /home and n
6 matches
Mail list logo
