File: TODO

package info (click to toggle)
nut 2.7.4-13
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 11,240 kB
  • sloc: ansic: 70,280; sh: 12,685; python: 2,235; cpp: 1,715; makefile: 1,387; perl: 705; xml: 40
file content (118 lines) | stat: -rw-r--r-- 4,560 bytes parent folder | download | duplicates (5)
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
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
NUT roadmap and ideas for future expansion
------------------------------------------

Here are some ideas that have come up over the years but haven't
been implemented yet.  This may be a good place to start if you're
looking for a rainy day hacking project.


Roadmap
~~~~~~~

2.6
^^^

This release is focused on the website and documentation rewrite, using
the excellent link:http://www.methods.co.nz/asciidoc[AsciiDoc].

2.8
^^^

This branch will focus on configuration and user interface improvements. 

3.0
^^^

This major transition will mark the final switch to a complete power
device broker.



Non-network "upsmon"
~~~~~~~~~~~~~~~~~~~~

Some systems don't want a daemon listening to the network.  This can be
for security reasons, or perhaps because the system has been squashed
down and doesn't have TCP/IP available.  For these situations you could
run a driver and program that sits on top of the driver socket to do
local monitoring.

This also makes monitoring extremely easy to automate - you don't need
to worry about usernames, passwords or firewalling.  Just start a driver
and drop this program on top of it.

- Parse ups.conf and open the state socket for a driver
- Send DUMPALL and enter a select loop
- Parse SETINFOs that change ups.status
- When you get OB LB, shut down

Completely unprivileged upsmon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

upsmon currently retains root in a forked process so it can call the
shutdown command.  The only reason it needs root on most systems is that
only privileged users can signal init or send a message on /dev/initctl.

In the case of systems running sysvinit (Slackware, others?), upsmon
could just open /dev/initctl while it has root and then drop it
completely.  When it's time to shut down, fire a control structure at
init across the lingering socket and tell it to enter runlevel 0.

This has been shown to work in local tests, but it's not portable.  It
could only be offered as an option for those systems which run that
flavor of init.  It also needs to be tested to see what happens to
the lingering fd over time, such as when init restarts after an upgrade.

For other systems, there is always the possibility of having a suid
program which does nothing but prod init into starting a shutdown.  Lock
down the group access so only upsmon's unprivileged user can access it,
and make that your SHUTDOWNCMD.  Then it could drop root completely.

Chrooted upsmon
~~~~~~~~~~~~~~~

upsmon could run the network monitoring part in a chroot jail if it had
a pipe to another process running outside for NOTIFY dispatches.  Such a
pipe would have to be constructed extremely carefully so an attacker
could not compromise it from the jailed process.

A state machine with a tightly defined sequence could do this safely.
All it has to do is dispatch the UPS name and event type.

	[start] [type] [length] <name> [stop]

Monitor program with interpreted language
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Once in awhile, I get requests for a way to shut down based on the UPS
temperature, or ambient humidity, or at a certain battery charge level,
or any number of things other than an "OB LB" status.  It should be
obvious that adding a way to monitor all of that in upsmon would bloat
upsmon for all those people who really don't need anything like that.

A separate program that interprets a list of rules and uses it to
monitor the UPS equipment is the way to solve this.  If you have a
condition that needs to be tested, add a rule.

Some of the tools that such a language would need include simple
greater-than/less-than testing (if battery.charge < 20), equivalence
testing (if ups.model = "SMART-UPS 700"), and some way to set and clear
timers.

Due to the expected size and limited audience for such a program, it
might have to be distributed separately.

NOTE: Python may be a good candidate.

Sandbox
~~~~~~~

- check to refresh and integrate the https://alioth.debian.org/pm/?group_id=30602[tasks] list
and https://alioth.debian.org/tracker/?atid=411545&group_id=30602&func=browse[feature requests] list from Alioth
- add "Generic ?Ascii? driver": I've got to think more about that, but the recent
solar panel driver, and the powerman internal approach of a generic engine with
a scripting interface is a cool idea.
Ref http://powerman.svn.sourceforge.net/viewvc/powerman/trunk/etc/apcpdu.dev?revision=969&view=markup
- integrate the (future) new powerman LUA engine (maybe/mustbe used for the driver above?)
for native PDU support
- see how we can help and collaborate with DeviceKit-power