summaryrefslogtreecommitdiff
path: root/debian/ifplugd.templates
blob: 0cf766ae4124f307a878b20b19b37f47a6d142dd (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Template: ifplugd/interfaces
Type: string
Default: 
_Description: static interfaces to be watched by ifplugd:
 Specify the interfaces to control here, separated by spaces. Ifplugd
 processes will be started for each of these interfaces when the ifplugd
 initscript is called with the "start" argument. You may use the magic
 string "auto" to make the initscript start or stop ifplugd processes for
 ALL eth and wlan interfaces that are available according to
 /proc/net/dev.  Note that the list of interfaces appearing in
 /proc/net/dev may depend on which kernel modules you have loaded.
 .
 You should not add interfaces that are hotplugged (USB or PCMCIA) here,
 you will be asked for those in the next question.

Template: ifplugd/hotplug_interfaces
Type: string
Default: 
_Description: hotplugged interfaces to be watched by ifplugd:
 Specify the hotplugged interfaces to control here, separated by spaces.
 .
 You may use the magic string "all" to make the hotplug script start an
 ifplugd process for any hotplugged interface.
 .
 Hotplugged interfaces are usually interfaces on PCMCIA or WLAN adapters.

Template: ifplugd/args
Type: string
Default: -q -f -u0 -d10 -w -I
_Description: arguments to ifplugd:
 You can give arguments to the ifplug daemon here. See the man page for a
 description or call ifplugd -h.

Template: ifplugd/suspend_action
Type: select
__Choices: none, suspend, stop
Default: stop
_Description: suspend behaviour:
 When you put your notebook into suspend mode, you can choose between three
 actions:
 .
 none: no action
 .
 suspend: this puts ifplugd into suspend mode. In this mode, ifplugd does
 not check the link status. This is necessary for some broken network
 drivers.
 .
 stop: this stops ifplugd. If the -q option is not given, ifplugd will stop
 the interface. After resume, it will be restarted. This makes sense if you
 use some mechanism (eg. guessnet or whereami) to detect your network
 environment, which may have changed while suspending.