Nut upsdev - Sep 2009 - IVT SCD support status

Rainer, Arjen

I was wandering around the code, and found that few things are missing
around the IVT code:
- no manpage,
- no entry in driver.list
- no device{mfr,model,type} in the code.

I was about to submit a patch to address the above (ready to commit), but
wanted first to get an update on the status. looking at the last thread,
it's a bit unclear... I'm also interested an upsc output.

looking at the driver, I'm also inclined in moving ups.status into
device.status (with 2.6 as a transition period).
ups and scd present the status the same way. and pdu could present it the
Powerman way, ie condensed like: off (1,2,4) on (3,5-8)

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20090906/82be8e65/attachment.htm>

arnaud,

sorry for not responding so long. in the meantime I managed to get the
serial ports on the atom mainboard working, but this "ground loop"
still persists, allthough there is neither a ground nor a loop (and
the IVT manufacturer isn't very helpful, unfortunately).

I tried to rpmbuild the current nut package under centos5 from a
fedora(?) SRPM, but as soon as I overcome an obstacle, the next one
shows up. I'm about to give up and just do a ./configure; make; make
install to get nut running in the next few days and hopefilly provide
you with the upcs output.

days are getting rapidly shorter now, leaving not enough sunlight to
charge the batteries to a level required to keep the server running.
so I better hurry ;-)

cu


AQ> Rainer, Arjen

AQ> I was wandering around the code, and found that few things are missing
AQ> around the IVT code:
AQ> - no manpage,
AQ> - no entry in driver.list
AQ> - no device{mfr,model,type} in the code.

AQ> I was about to submit a patch to address the above (ready to commit), but
AQ> wanted first to get an update on the status. looking at the last thread,
AQ> it's a bit unclear... I'm also interested an upsc output.

AQ> looking at the driver, I'm also inclined in moving ups.status into
AQ> device.status (with 2.6 as a transition period).
AQ> ups and scd present the status the same way. and pdu could present it the
AQ> Powerman way, ie condensed like: off (1,2,4) on (3,5-8)

AQ> cheers,
AQ> Arnaud


------------------------------------------------------------------------------
Unix gives you just enough rope to hang yourself -- and then a couple of more 
feet, just to be sure.
(Eric Allman)
------------------------------------------------------------------------------