similar to: new NUT release please!

On 9/10/2017 6:41 PM, Sam Varshavchik wrote: > Dutchman01 writes: > >> Hello all, >> >> ? >> >> I request a new NUT release as current dates back to March 9, 2016: NUT 2.7.4 >> >> The fact stays that not all distro?s use latest snapshots/commits from github >> dev tree. >> >> ? >> >> So please do release a new up to

And you can source build the current version from source on pretty much anything, thus negating any value of distro centric packaging . . . On September 10, 2017 4:20:49 PM CDT, Greg Vickers <daehenoc at iinet.net.au> wrote: >I'll take this hit: Dutchman01, why should there be a new version >released? Is there a significant problem with the current version, or >major

hi, I am still batteling with winbind, and frankly, i am getting desperate enough to long for a weekend without any computers in sight (that is bad for an addict) I know I probably make a small stuid blunder but still, I cant find it. The attachment is my smb.conf file. I created the needed paths, I even made sure the ermissions are set! I created asmbusers file with contains the following

I'll take this hit: Dutchman01, why should there be a new version released? Is there a significant problem with the current version, or major functionality that is missing? Releasing a new version for the sake of an updated version number isn't a reason for releasing an update. On 11/9/17 1:56 am, Dutchman01 wrote: > > Hello all, > > I request a new NUT release as

Dutchman01 writes: > Hello all, > > ? > > I request a new NUT release as current dates back to March 9, 2016: NUT 2.7.4 > > The fact stays that not all distro?s use latest snapshots/commits from github > dev tree. > > ? > > So please do release a new up to date version please. I updated Fedora's nut rpms with a custom rpm package that was built off the

Mike writes: > On 9/10/2017 6:41 PM, Sam Varshavchik wrote: > > Dutchman01 writes: > > > >> Hello all, > >> > >> ? > >> > >> I request a new NUT release as current dates back to March 9, 2016: NUT > 2.7.4 > >> > >> The fact stays that not all distro?s use latest snapshots/commits from > github > >>

On 09/11/2017 10:49 AM, Sam Varshavchik wrote: > Mike writes: > >> On 9/10/2017 6:41 PM, Sam Varshavchik wrote: >> > Dutchman01 writes: >> > >> >> Hello all, >> >> >> >> >> >> >> >> I request a new NUT release as current dates back to March 9, >> 2016: NUT 2.7.4 >> >> >> >> The

I have a TrippLite AVR550U that my company uses several individual Linux boxes in one large system, all running Ubuntu 18.04LTS, and all will be using the package version of nut - 2.7.4. In my scenario, our usage case is for the PCs to all shut down, followed by the individual UPSes, when mains power is removed from the whole system. (This isn't a typical setup for UPS, but it's what

Anyone familiar with Cyberpower's model numbers? I finally got sick of my Tripplite's USB port going south, all the time, so I'm looking to replace it. The HCL has an entry for a Cyberpower model CP1500AVRLCD. Not listed is the CP1500PFCLCD model, a newer, premium version of the unit; but the HCL does have an entry for the CP1000PFCLCD model. Pretty sure that the CP1500PFCLCD

Hi Raphael, btw, are you 2 bugs today a simple coincidence with my linkedIn invitation yesterday? ;-) 2008/10/4 Raphael Geissert <atomo64 at gmail.com>: > Package: nut > Version: 2.2.2-8 > Severity: wishlist > Tags: patch > > Attached is a patch adding "support" for tripplite's avr750u UPS. > Issues: > * productid still needs to be specified in

Hi, I've been using TrippLite's PowerAlert software with my RM2200XL2U rack system and my APC BackUPS desktop systems. Unfortunately it doesn't work with openSUSE 10.2 (the software has problems with the serial port and UPS interfaces on openSUSE 10.2), so I've been looking at other options. I see that openSUSE 10.2 includes NUT, and it appears to work with my TrippLite UPS via

Hello Nut Devs, I'm working with usbhid-ups and a Tripplite OMNI1000LCD. I used a USB packet sniffer to discover something cool about the watchdog feature in this unit. (not sure if the other OMNI-X-LCD models work the same or not.) Basically there's a single HID variable at Report ID 0x52 (UPS.OutletSystem.Outlet.ffff0092) that's one byte (0-255 int) and it contains the Watchdog

I think I'm going to have the slightly rejigger the tripplite-hid.c driver to 'properly' support all of the data I know about it's outlets. A given UPS may have 'n' output loads. I could have 5, I could have 10, I won't know until I actually ask the UPS. But in order to use the hid to nut struct, I'm actually going to have to modify that struct dynamically, or

I'm having trouble with a TrippLite SU3000XLCD. I'm using a Raspberry Pi running Raspbian (wheezy) with NUT 2.6.4. I can monitor my older TrippLite UPSs, mostly SU1000RT2Us, with this Pi and a USB to serial adapter. My first thought with the SU3000XLCD was to use the USB port instead of the serial port as that's the "modern" thing to do. When I plugged the USB cable in

Dean K. Gibson wrote: > > My Belkin UPS 1000 failed about a month ago; all of a sudden it > reported a battery failure. Since the Belkin logs showed this as in > instant transition from 99% to 22%, I assume a circuit board failure, > not a battery failure. Similarly, one Belkin UPS 500 circuit board > failed after I used my 100W amateur radio transmitter (not connected to

Hi, There's a rather serious problem with the Oddcast DSP for Winamp, when you stream in vorbis format over icecast2, it drops ~ 1/2 sec of near the beginning of every song except the first. I tracked this down, it turns out oddcast drops the last vorbis page of every stream. (The DSP doesn't receive the new metadata until after the song has been playing for a second or two, which is

> Everything looks fine apart from ups.beeper.status always shows enabled > even if the status bit fom the ups has changed state. Probably because the driver updates the beeper status only every 'pollfreq' (default 30) seconds, so it may have missed the change. > After more testing the indexes work as follows > > 0x0a = load.on / cancel.shutdown.stayoff /

On 06/24/2017 04:52 AM, Charles Lepple wrote: > On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote: >> "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" >> but my device (SU2200RTXLCD2U) is supported, as clearly state here. > No, the HCL also mentions "protocol 4001". For Tripp-Lite,

Finally I got time to test this. >>> Can you post the output of upsc, and note if any of those values look >>> wrong? serwer2:/tmp/nut-fabula # upsc myups battery.charge: 100 battery.voltage: 13.10 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.model: 500VA UPS device.type: ups driver.name: nutdrv_qx driver.parameter.pollfreq: 30

Can anyone help getting a Tripplite SU2200XL to work with nut 2.0.3 using the supplied serial cable? Starting the ups service yields: Starting tripplitesu: Network UPS Tools - Tripp Lite SmartOnline driver 0.02 (2.0.3) Unable to detect Tripp Lite SmartOnline UPS on port /dev/ttyS0 I also have Tripplite's PowerAlert 12 software installed and when run it finds the UPS without a problem. So