1UPSD.CONF(5) NUT Manual UPSD.CONF(5)
2
6 upsd.conf - Configuration for Network UPS Tools upsd
7
9 upsd uses this file to control access to the server and set some other
10 miscellaneous configuration values. This file contains details on
11 access controls, so keep it secure. Ideally, only the upsd process
12 should be able to read it.
13
15 "MAXAGE seconds"
16 upsd usually allows a driver to stop responding for up to 15
17 seconds before declaring the data "stale". If your driver takes a
18 very long time to process updates but is otherwise operational, you
19 can use MAXAGE to make upsd wait longer.
20 Most users should leave this at the default value.
22 "STATEPATH path"
24 Tell upsd to look for the driver state sockets in path rather than
25 the default that was compiled into the program.
26 "LISTEN interface port"
28 Bind a listening port to the interface specified by its Internet
29 address. This may be useful on hosts with multiple interfaces. You
30 should not rely exclusively on this for security, as it can be
31 subverted on many systems.
32 Listen on TCP port port instead of the default value which was
34 compiled into the code. This overrides any value you may have set
35 with configure --with-port. If you don’t change it with configure
36 or this value, upsd will listen on port 3493 for this interface.
37 Multiple LISTEN addresses may be specified. The default is to bind
39 to 127.0.0.1 if no LISTEN addresses are specified (and ::1 if IPv6
40 support is compiled in).
41 LISTEN 127.0.0.1
43 LISTEN 192.168.50.1
44 LISTEN ::1
45 LISTEN 2001:0db8:1234:08d3:1319:8a2e:0370:7344
46 This parameter will only be read at startup. You’ll need to restart
48 (rather than reload) upsd to apply any changes made here.
49 "MAXCONN connections"
51 This defaults to maximum number allowed on your system. Each UPS,
52 each LISTEN address and each client count as one connection. If the
53 server runs out of connections, it will no longer accept new
54 incoming client connections. Only set this if you know exactly what
55 you’re doing.
56 "CERTFILE certificate file"
58 When compiled with SSL support with OpenSSL backend, you can enter
59 the certificate file here. The certificates must be in PEM format
60 and must be sorted starting with the subject’s certificate (server
61 certificate), followed by intermediate CA certificates (if
62 applicable_ and the highest level (root) CA. It should end with the
63 server key. See docs/security.txt or the Security chapter of NUT
64 user manual for more information on the SSL support in NUT.
65 "CERTPATH certificate database"
67 When compiled with SSL support with NSS backend, you can enter the
68 certificate path here. Certificates are stored in a dedicated
69 database (splitted in 3 files). Specify the path of the database
70 directory.
71 "CERTIDENT certificate name database password"
73 When compiled with SSL support with NSS backend, you can specify
74 the certificate name to retrieve from database to authenticate
75 itself and the password required to access certificate related
76 private key.
77 "CERTREQUEST certificate request level"
79 When compiled with SSL support with NSS backend and client
80 certificate validation (disabled by default, see
81 docs/security.txt), you can specify if upsd requests or requires
82 client’s' certificates. Possible values are :
83 · 0 to not request to clients to provide any certificate
85 · 1 to require to all clients a certificate
87 · 2 to require to all clients a valid certificate
89
91 upsd(8), nutupsdrv(8), upsd.users(5)
92
94 The NUT (Network UPS Tools) home page: http://www.networkupstools.org/
95Network UPS Tools 2.7.3. 12/29/2015 UPSD.CONF(5)