diff options
| author |   Maciej S. Szmigiero <mail@maciej.szmigiero.name> | 2017-11-29 20:49:27 +0100 |
|---|---|---|
| committer |   Robin H. Johnson <robbat2@gentoo.org> | 2018-07-11 23:51:03 -0700 |
| commit | 6f261f1beec1ecbfe7ec39ae33b5a7f947292f6e (patch) | |
| tree | b375ef3ba0aa1affbc71adf351d768220a045a14 /sh | |
| parent | doc: usage example for wireguard (diff) | |
| download | netifrc-6f261f1beec1ecbfe7ec39ae33b5a7f947292f6e.tar.gz netifrc-6f261f1beec1ecbfe7ec39ae33b5a7f947292f6e.tar.bz2 netifrc-6f261f1beec1ecbfe7ec39ae33b5a7f947292f6e.zip | |
init.d/net.lo: add a configurable presence timeout
Sometimes one may want to wait for a particular interface to show up
when starting its service.
For example if a "net.foo" service is in the "default" runlevel so it
provides (or co-provides) the "net" service and it takes a while for the
"foo" interface to initialize and show up in the system during boot this
interface initialization will race with starting of this "net.foo" service
by the service manager - if the interface hasn't shown up yet the service
won't be able to start (and so will services that depend on it).
This setting specifies how long we'll wait for an interface to show up
in this case (in seconds).
For backward-compatibility the default is 0 (don't wait at all) - this
matches the existing behavior of netifrc, so existing deployments aren't
affected by this change.
This new setting is similar to an already present "wait for carrier
timeout" setting.
Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
(cherry picked from commit 64f33a2032b4972a25cad6405678f678a5a269ff)
Closes: https://github.com/gentoo/netifrc/pull/28
Diffstat (limited to 'sh')
0 files changed, 0 insertions, 0 deletions