Le 12/12/2018 à 14:18, Dr. Nikolaus Klepp a écrit :
> Am Mittwoch, 12. Dezember 2018 schrieb Didier Kryn:
>> Le 12/12/2018 à 13:58, Dr. Nikolaus Klepp a écrit :
>>> Am Dienstag, 11. Dezember 2018 schrieb Gonzalo Pérez de Olaguer Córdoba:
>>>> Hi Michael K.
>>>>
>>>> El Fri, 7 Dec 2018 12:45:11 +0100
>>>> "Michael K." <michael@???> escribió:
>>>>
>>>>> After a Dev1 Setup on a Laptop (whit eth0), i have to wait a long time
>>>>> for the eth0 on "cold boot".
>>>>>
>>>>> I "cold boot" my Laptop
>>>>> I look to the "Boot Messages"
>>>>> I see the following Msg:
>>>>>
>>>>> Configuring Network Interfaces ifup: Waiting for Lock on
>>>>> /run/network/ifstat.eth0
>>>>>
>>>>> After 2 or 3 minutes to wait, the Laptop boot up,
>>>> Just in case this could help, I've been having this same *symptom*
>>>> on KVM virtual machines running ascii.
>>>>
>>>> My situation was eth0 being configured through DHCP and using the
>>>> dhcp client from the isc-dhcp-client package, which sends (maybe buggy)
>>>> DHCPDECLINE packets.
>>>>
>>>> My workaround was to replace isc-dhcp-client with pump.
>>>>
>>>> If you want more details, tell me and I will continue writing.
>>>>
>>>> Bye,
>>>> Salo.
>>>>
>>> Now this is a neet tick! It also solves the issue that booting hangs on the said message when no network cable is attached to eth0.
>>>
>>> Nik
>>>
>>     Is it as simple as apt-get remove isc-dhcp-client; apt-get install
>> pump ?
> Yes, but I first installed pump and then purged isc-dhcp-client.
>
>

    This does not suppress at all the delay caused by waiting on the
eth0 lock. Which makes sense because detecting the status of eth0
precedes running dhcp requests on it.

    In addition, if you configure your network with net-tools and
remove isc-dhcp-client, you loose all connectivity because net-tools
invokes dhclient to make dhcp requests. Since pump and isc-dhcp-client
aren't mutually exclusive packages, it is clear that pump does not
provide a drop-in replacement for dhclient.

    Not clear how to configure the interfaces file for ifupdown to work
with pump because the logic isn't the same as dhclient: dhclient has one
daemon per interface, while the pump daemon manages all interfaces in
the same time. This would IMHO deserve a tutorial.

    Didier