search for: epdus

...e <https://github.com/networkupstools/nut/issues/185> * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM <https://github.com/networkupstools/nut/issues/187> * #190: upsd: NSS SSL only working in debug mode <https://github.com/networkupstools/nut/issues/190> * eaton_epdus branch: <https://github.com/networkupstools/nut/tree/eaton-epdus> Most of these are from the GitHub 2.7.3 milestone: https://github.com/networkupstools/nut/issues?q=milestone%3A2.7.3 #93: The scope of this issue is a bit broad (encompassing a Gen3 dummy-ups driver, etc) but for 2.7.3, I thi...

...//github.com/networkupstools/nut/issues/185> > * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM <https://github.com/networkupstools/nut/issues/187> > * #190: upsd: NSS SSL only working in debug mode <https://github.com/networkupstools/nut/issues/190> > * eaton_epdus branch: <https://github.com/networkupstools/nut/tree/eaton-epdus> > > Most of these are from the GitHub 2.7.3 milestone: https://github.com/networkupstools/nut/issues?q=milestone%3A2.7.3 A quick status update: * #93: most of the DDL stuff is merged; anything else can wait for 2.7.4....

...a bit on adding PDU (http://en.wikipedia.org/wiki/Power_distribution_unit) support in NUT. Some of you might have seen the Powerman thread, which also deals with adding more PDUs support: http://powerman.sourceforge.net/supported.html The result is that we now have support for 2 Eaton | Powerware ePDUs (Managed and Monitored iirc, check http://www.epdu.com). I plan on adding the 2 other models soon. It is using snmp-ups and I've attached an upsc/upscmd output of the managed unit for info. The patch isn't commited yet, but it's limited to adding a xx-mib.h file, and some doc update. I&...

...tworkupstools/nut/issues/185> > * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM < > https://github.com/networkupstools/nut/issues/187> > * #190: upsd: NSS SSL only working in debug mode < > https://github.com/networkupstools/nut/issues/190> > * eaton_epdus branch: < > https://github.com/networkupstools/nut/tree/eaton-epdus> > > Most of these are from the GitHub 2.7.3 milestone: > https://github.com/networkupstools/nut/issues?q=milestone%3A2.7.3 > > #93: The scope of this issue is a bit broad (encompassing a Gen3 dummy-ups >...

...s/nut/issues/185> > > * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM < > https://github.com/networkupstools/nut/issues/187> > > * #190: upsd: NSS SSL only working in debug mode < > https://github.com/networkupstools/nut/issues/190> > > * eaton_epdus branch: < > https://github.com/networkupstools/nut/tree/eaton-epdus> > > > > Most of these are from the GitHub 2.7.3 milestone: > https://github.com/networkupstools/nut/issues?q=milestone%3A2.7.3 > > A quick status update: > > * #93: most of the DDL stuff is merg...

...can already see the results with: * Arjen and the new blazer* drivers, along with his work the netxml-ups (prev. mge-xml) driver, * Kjell adding the awaited Load Segments support in bcmxcp (outlet.* collection, aka NUT Powersave feature) * myself and the various PDUs supported (based on Eaton ePDUs work at first!) - NUT will be tested against *all* the Powerware / MGE Office Protection Systems / Centralion systems - resources will be setup so that NUT developers can access to many live systems for development and testing, - a buildbot farm will be setup so that our QA get reinforced, - I shou...

I have an idea for my shutdown process at home. My goal: maximize the network run-time. At present, the UPS has a run-time of about 57 minutes. This is my idea: * shutdown the servers after 15 minutes of downtime (for me, that's when battery.runtime hits 40) * leave the network gear (switches, firewall, wifi) running so I can continue with Internet access Optionally: * when we get down to

...ls (i.e *synchronous=auto*). This means that all data # are pushed by the driver on the communication socket to # upsd (Unix socket on Unix, Named pipe on Windows) without # waiting for these data to be actually consumed. With # some HW, such as ePDUs, that can produce a lot of data, # asynchronous mode may cause some congestion, resulting in # the socket to be full, and the driver to appear as not # connected. By enabling the 'synchronous' flag # (value = 'yes'), the driver wi...