1NUT.CONF(5) NUT Manual NUT.CONF(5)
2
3
4
6 nut.conf - UPS definitions for Network UPS Tools
7
9 This file attempts to standardize the various files being found in
10 different installations, like /etc/default/nut on Debian based systems
11 and /etc/sysconfig/ups on RedHat based systems.
12
13 Distribution’s init script should source this file in order to
14 determine which components have to be started.
15
16 Blank lines are ignored. Lines with a hash (#) character at the 1st
17 position of the line are ignored, too. They can be used to add
18 comments.
19
21 MODE
22 Required. Recognized values are none, standalone, netserver and
23 netclient. Defaults to none.
24
25 none
26 Indicates that NUT should not get started automatically,
27 possibly because it is not configured or that an Integrated
28 Power Management or some external system, is used to startup
29 the NUT components.
30
31 standalone
32 Addresses a local only configuration, with 1 UPS protecting the
33 local system. This implies to start the 3 NUT layers (driver,
34 upsd and upsmon), with the related configuration files. This
35 mode can also address UPS redundancy.
36
37 netserver
38 Like the standalone configuration, but also possibly need one
39 or more specific LISTEN directive(s) in upsd.conf. Since this
40 MODE is open to the network, a special care should be applied
41 to security concerns.
42
43 netclient
44 When only upsmon is required, possibly because there are other
45 hosts that are more closely attached to the UPS, the MODE
46 should be set to netclient.
47
48 UPSD_OPTIONS
49 Optional. Set upsd specific options. See upsd(8) for more details.
50 It is ignored when MODE above indicates that no upsd should be
51 running.
52
53 UPSMON_OPTIONS
54 Optional. Set upsmon specific options. See upsmon(8) for more
55 details. It is ignored when MODE above indicates that no upsmon
56 should be running.
57
58 POWEROFF_WAIT
59 Optional. At the end of an emergency system halt, the upsmon master
60 will signal the UPS to switch off. This may fail for a number of
61 reasons. Most notably is the case that mains power returns during
62 the shutdown process. See the section "Power races" in
63 /usr/share/doc/nut/docs/shutdown.txt.gz. The system will wait this
64 long for the UPS to cut power, and then reboot. It should be long
65 enough to exhaust the batteries, in case line power continues to be
66 unavailable. On the other hand, it should not be so long that the
67 system remains offline for an unreasonable amount of time if line
68 power has returned. See sleep(1) for compatible time syntax. If you
69 specify the time in seconds, use the "s" suffix.
70
71 Warning
72 this workaround might be dangerous under some circumstances. Please
73 read http://bugs.debian.org/358696 for more details.
74
76 # /etc/nut/nut.conf. See nut.conf(5)
77
78 MODE = none
79
80 UPSD_OPTIONS = ""
81
82 UPSMON_OPTIONS = ""
83
84 # POWEROFF_WAIT = 15m
85
87 An init script, such as /etc/init.d/nut, is expected to source this
88 file in order to determine which component(s) has to be started.
89
91 ups.conf(5), upsd.conf(5), upsd.users(5), upsmon.conf(5)
92
94 The NUT (Network UPS Tools) home page: http://www.networkupstools.org/
95
96
97
98Network UPS Tools 09/15/2011 NUT.CONF(5)