02.12.2015 Views

Network UPS Tools User Manual

Network UPS Tools User Manual

Network UPS Tools User Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Network</strong> <strong>UPS</strong> <strong>Tools</strong> <strong>User</strong> <strong>Manual</strong> 83 / 84<br />

J.4.4 July 2003: third stable tree: NUT 1.4.0<br />

On July 25, 2003, 1.4.0 was released. It contained support for both the old "REQ" style protocol (with names like STATUS), and<br />

the new "GET" style protocol (with names like ups.status). This tree is provided to bridge the gap between all of the old releases<br />

and the upcoming 2.0.<br />

2.0 will be released without support for the old REQ/STATUS protocol. The hope is that client authors and those who have<br />

implemented their own monitoring software will use the 1.4 cycle to change to the new protocol. The 1.4 releases contain a lot<br />

of compatibility code to make sure both work at the same time.<br />

J.4.5 July 2003: pushing towards 2.0<br />

1.5.0 forked from 1.4.0 and was released on July 29, 2003. The first changes were to throw out anything which was providing<br />

compatibility with the older versions of the software. This means that 1.5 and the eventual 2.0 will not talk to anything older than<br />

1.4.<br />

This tree continues to evolve with new serial routines for the drivers which are intended to replace the aging upscommon code<br />

which dates back to the early 0.x releases. The original routines would call alarm and read in a tight loop while fetching<br />

characters. The new functions are much cleaner, and wait for data with select. This makes for much cleaner code and easier<br />

strace/ktrace logs, since the number of syscalls has been greatly reduced.<br />

There has also been a push to make sure the data from the <strong>UPS</strong> is well-formed and is actually usable before sending updates out<br />

to upsd. This started during 1.3 as drivers were adapted to use the dstate functions and the new variable/command names. Some<br />

drivers which were not converted to the new naming scheme or didn’t do sanity checks on the incoming <strong>UPS</strong> data from the serial<br />

port were dropped from the tree.<br />

This tree was released as 2.0.0.<br />

J.5 networkupstools.org<br />

J.5.1<br />

November 2003: a new URL<br />

The bandwidth demands of a project like this have slowly been forcing me to offload certain parts to other servers. The download<br />

links have pointed offsite for many months, and other large things like certain <strong>UPS</strong> protocols have followed. As the traffic grows,<br />

it’s clear that having the project attached to exploits.org is not going to work.<br />

The solution was to register a new domain and set up mirrors. There are two initial web servers, with more on the way. The<br />

main project URL has changed from http://www.exploits.org/nut/ to http://www.networkupstools.org. The actual<br />

content is hosted on various mirrors which are updated regularly with rsync, so the days of dribbling bits through my DSL should<br />

be over.<br />

This is also when all of the web pages were redesigned to have a simpler look with fewer links on the left side. The old web<br />

pages used to have 30 or more links on the top page, and most of them vanished when you dropped down one level. The links<br />

are now constant on the entire site, and the old links now live in their own groups in separate directories.<br />

J.6 Second major version<br />

J.6.1 March 2004: NUT 2.0.0<br />

NUT 2.0.0 arrived on March 23, 2004. The jump to version 2 shows the difference in the protocols and naming that happened<br />

during the 1.3 and 1.5 development series. 2.0 no longer ships with backwards compatibility code, so it’s smaller and cleaner<br />

than 1.4.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!