Re: [solved] Re: Message at boot: `A start job is running for LSB: Raise network interfaces'

[Christian Seiler <christian@iwakd.de>]

Am 2015-07-07 14:19, schrieb Rodolfo Medina:
> > You have an interface configured to use WPA and DHCP. This *WILL* 
> > take a
> > few seconds. First, your adapter needs to find the Access Point,
> > establish a connection and authenticate using the pre-shared key. 
> > Only
> > once that link is established, can the DHCP sequence begin. This
> > involves broadcasting a request packet and then listening for 
> > several
> > seconds (this is repeated at varying intervals). Once an acceptable
> > acknowledgement packet is received, then hook scripts are run to set 
> > IP,
> > DNS, NTP etc. Only once they are done, can the interface be 
> > considered
> > "ready".
>
> I see.  But on another machine of mine, I have the same configuration 
> and the
> problem doesn't occur.

Well, it depends on how long the interface setup takes: some
hardware and driver combinations just might take a bit longer than
others to set everything up.

systemd has a built-in timeout that if it has to wait longer than
X seconds (X being 10 or 15 or so) for a job to complete, it will
display some information so that the user has an idea of what's
going on with their system (default job timeout before systemd
considers a job failed is 90s, and many people might think their
system to already have crashed, were they forced to wait that long
before seeing any output).

Note that since you now use allow-hotplug, be aware that you should
be careful with that: if you have ANY boot service that requires an
active network interface, they won't work anymore, even if the setup
of the interface is fast, since systemd will then not order anything
relative to network availability anymore. So if you have NFS
filesystems or similar: don't use allow-hotplug, always use auto!

Christian