Penguin
Recent Changes
Annotated edit history of upsc(8) version 1, including all changes. View license author blame.
Rev Author # Line
1 perry 1 UPSC
2 !!!UPSC
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 OPTIONS
7 DIAGNOSTICS
8 BUGS
9 SEE ALSO
10 ----
11 !!NAME
12
13
14 upsc - example lightweight UPS client
15 !!SYNOPSIS
16
17
18 __upsc__ ''ups''
19 !!DESCRIPTION
20
21
22 __upsc__ is provided as a quick way to poll the status of
23 a UPS server. It can be used inside shell scripts and other
24 programs that need UPS data but don't want to include the
25 full interface.
26
27
28 Note that upsc polls via UDP which is fundamentally
29 unreliable and may not function at all over lossy networks.
30 For reliable communications over TCP, see
31 upsct(8).
32 !!OPTIONS
33
34
35 ''ups''
36
37
38 Display the status of that UPS. The format for this option
39 is [[upsname@]hostname[[:port].
40
41
42 For example,
43 upsd__(8) running on port 1234.
44
45
46 Using an argument like
47 !!DIAGNOSTICS
48
49
50 upsc will either print a list of all supported variables and
51 their values on the UPS or an error message. If you receive
52 an error, make sure you have specified a valid UPS on the
53 command line, that upsd(8) is really running on the
54 other host and that no firewalls are blocking
55 you.
56 !!BUGS
57
58
59 UDP connections over many hops tend to break.
60 !!SEE ALSO
61
62
63 upsd(8), upsct(8)
64
65
66 __Internet resources:__
67
68
69 The NUT (Network UPS Tools) home page:
70 http://www.exploits.org/nut/
71
72
73 NUT mailing list archives and information:
74 http://lists.exploits.org/
75 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.