UPSD(8) Network UPS Tools (NUT) UPSD(8)
upsd - UPS information server
upsd [-p port] [-t port] [-i interface] [-f] [-u user] [-c command]
upsd is responsible for serving the data from the drivers to the clients. It listens on
network ports and delivers the data from the state files or shared memory used by the
drivers. It also conveys administration messages from the clients such as upsrw(8) or
upscmd(8) back to the drivers.
This program is essential, and must be running at all times to actually make any use out
of the drivers and clients.
Controls in the configuration files allow you to limit access to the server, but you
should also use a firewall for extra protection. Client processes such as upsmon(8) trust
upsd for status information about the UPS hardware, so keep it secure.
Send command to the background process as a signal. Valid commands are:
reload - reread configuration files
stop - stop process and exit
-f Stay in the foreground for testing.
-h Display the help text.
Bind the listeners to the interface specified by its internet address. This may be
useful in situations with internal and external interfaces on the same host.
Run the UDP and TCP listeners on that port. This overrides any value you may have
set with 'configure --with-port'. If you don't change it with configure or this
switch, upsd will listen on port 3493.
Run just the TCP listener on that port. If you want the TCP and UDP listeners on
different ports for some reason, use -p, then follow it with -t.
Switch to user user after startup if started as root. This overrides whatever you
may have compiled in with 'configure --with-user'.
-V Display the version of the program.
upsd can reload its configuration files without shutting down the process if you send it a
SIGHUP or start it again with '-c reload'. This only works if the background process is
able to read those files. Since upsd gives up root after reading the files for the first
time, this may not always be the case.
If you think that upsd can't reload, check your syslogs for error messages. If it's com-
plaining about not being able to read the files, then you need to adjust your system to
make it possible. Either change the permissions on the files, or run upsd as another user
that will be able to read them.
DO NOT make your upsd.conf world-readable, as it contains passwords and some evil person
could pretend to be your master upsmon and command your systems to shut down.
upsd expects the drivers to update their status regularly. By default, they must be
refreshed every 15 seconds. After that, the UPS is declared "stale" and no more informa-
tion will be provided to the clients.
If upsd complains about staleness when you start it, then either your driver or configura-
tion files are probably broken. Be sure that the driver is actually running, and that the
UPS definition in ups.conf(5) is correct.
The general upsd configuration file is upsd.conf(5). The administrative functions like
SET and INSTCMD for users are defined and controlled in upsd.users(5). UPS definitions
are found in ups.conf(5).
upsc(8), upscmd(8), upsrw(8), upslog(8), upsmon(8)
upsset.cgi(8), upsstats.cgi(8), upsimage.cgi(8)
nutupsdrv(8), apcsmart(8), bcmxcp(8), belkin(8), bestferrups801-807(8), bestuferrups(8),
bestups(8), cyberpower(8), dummycons(8), dummyups(8), everups(8), fentonups(8), gener-
icups(8), hidups(8), hp(8), masterguard(8), mge-ellipse(8), mge-utalk(8), microdowell(8),
newapc(8), powercom(8), powernet(8), sec(8), snmp-ups(8), tripplite(8), victronups(8)
The NUT (Network UPS Tools) home page: http://www.exploits.org/nut/
NUT mailing list archives and information: http://lists.exploits.org/
Sat Aug 31 2002 UPSD(8)