Re: in /etc/network/interfaces: "auto" vs "allow-hotplug"
- Date: Mon, 25 Sep 2017 11:40:12 -0400
- From: Gene Heskett <gheskett@xxxxxxxxxxx>
- Subject: Re: in /etc/network/interfaces: "auto" vs "allow-hotplug"
On Monday 25 September 2017 09:00:51 Greg Wooledge wrote:
> On Sat, Sep 23, 2017 at 08:56:49PM -0700, Rick Thomas wrote:
> > I have two machines (out of a group of ten) that will not bring up
> > their ethernet interface at boot time if the interfaces is of type
> > “allow-hotplug”. When I change that to “auto” the interface comes
> > up at boot with no problem…
> > The remaining eight machines have no problem with allow-hotplug.
> > (which is the default as setup by the d-i)
> The basic difference is the order in which services get loaded at
> boot time, and whether the services wait for something, or just go.
> An interface marked "auto" will be waited-for by services that are
> configured to wait for interfaces to be up. E.g. mounting NFS file
> systems, or starting an NFS server.
> An interface marked "allow-hotplug" is considered nonessential or
> transient, and the core OS services won't wait for it before starting.
Thank you Greg. Its not possible to check that because a new minimal
stretch install for an arm64 has no man command. If the man page can be
found, zmore can read it but thats such an eyeball assault you lose
track of what it was you wanted to check.
Cheers, Gene Heskett
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>