similar to: Environment Variables

The if() statement always evaluated to true. Detected by "cppcheck", not tested on real hardware. Signed-off-by: Thomas Jarosch <thomas.jarosch at intra2net.com> --- drivers/rhino.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/rhino.c b/drivers/rhino.c index ca66169..e478bcb 100644 --- a/drivers/rhino.c +++ b/drivers/rhino.c @@ -187,7 +187,7

Hello! I have installed the nut package from the OpenBSD 4.4 packages tree, nut-2.2.1p0 I have a new APC Smart-UPS 750 which I plan to connect via USB. When I try to start the usbhid-ups i get debug level is '2' upsdrv_initups... No appropriate HID device found No matching HID UPS found for almost anything i try. OpenBSD detects my UPS and assigns it to a device and it can be seen

OS: Debian 3.16.36 Nut version: 2.7.4 from the ?stretch? distribution (this was to solve another problem ? which it did) Install method: apt-get Device: TRIPPLITE SMART1300LCDT using usbhid-ups driver Problem: I keep getting the message UPS tripplite at localhost is unavailable If I do? service nut-server stop service nut-server start Then everything is fine again for a while.

I tried viewing your link, but it returns a 404 error. It also doesn't seem to have a valid certificate. Could you send the correct link please? On Thu, Oct 6, 2016 at 9:14 PM, Stuart Gathman <stuart at gathman.org> wrote: > On 10/06/2016 07:26 PM, Lane Russell wrote: > > ?? > Syslog after server loses sight of UPS: > Oct 6 17:29:01 kvm usbhid-ups[3529]:

Hi can anyone please help. I have two linux servers both with static IPs not using NAT. My slave can't connect to my host. Whatever I try. I have the same setup also on my LAN with two other machines and they talk to each other and work great. But my two machines with their own static IPs don't want to play. I've used the same settings for these as I have on my LAN, with a master

I just hooked up an old Best Fortress (with new batteries). Those things are built like a tank, and it works out of the box in Fedora 14 (nut-2.6.2) thanks to the bestfortress driver still in the project. It had disappeared for 2.0, but I sent it in for 2.2, and you guys kept it going. -- Stuart D. Gathman <stuart at bmsi.com> Business Management Systems Inc. Phone: 703

Hi Charles, Thank you so much for getting back to me. I should have given you a bit of background in my last message but I'm actually doing this for my grandmother's benefit! She has Dementia and lives on her own so we want to be notified if she has a power cut... I'd hate to think she might be stumbling around in the dark (which has happened before)! In terms of stopping the older

Or just set up sane firewall rules to allow the two to talk, but block external traffic. I have run this way for years - all add'rs ar IANA in a subnet block, and just that block is open locally, and all other external IP's severely restricted, and NUT works great . . . - Tim On September 12, 2016 11:47:28 AM CDT, "Stuart D. Gathman" <stuart at gathman.org> wrote: >On

Hello, I spent time this weekend trying to compile wine on my home computer. The machine is a Sun Microsystems X86 box running Solaris 10 operating system. I have the freeware including gmake and gcc installed and in the path. I managed to get ./configure to run, but had to use --exclude-network-build and --exclude-pp-build or something like that to make it work. make depend &&

On 2019-02-16 12:41 p.m., Stuart D. Gathman wrote: > On Sat, 16 Feb 2019, James wrote: > >> These changed: >> battery.runtime: >> ups.load: >> >> Is the battery dead again? >> Do I need a new UPS? > > Compare the upsc output with the screen/led display on the UPS.  If they > are in agreement, then there is no problem with NUT.  Your issue is

The battery was replaced in December and the output from upsc was: $ upsc desktop_ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1020 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS CP850AVRLCD device.type: ups driver.name: usbhid-ups

I've made some progress getting this Tripplite to work: http://gathman.org/2016/07/30/Standard_Schmandard/ Basically, plug it into a USB hub that actually implements USB2.0, then power cycle the port when it hangs. It does seem to be a hardware problem with the USB controller. On 05/24/2016 09:06 AM, Charles Lepple wrote: > On May 22, 2016, at 10:18 AM, Stuart Gathman wrote: >> I

Hello, sorry for disturbing the list but i am just an "amateur" and have problem to configure the nut network For the config I have one NUT server and want ot have two clients The client on the NUT server is running well but the client on the network is not able to connect to the server The NUT server is an ubuntu 18.04 machine. If I run the nut monitor on the server, the monitor

Our server has 2 UPS on 2 PSUs. At 8am, someone unplugged one UPS. At 8:10, they plugged it back in, but turned off the load - presumably to stop the beeping. So the system is still up on 1 PSU, and can talk to both UPS. Can't I turn on the load via USB? upsc output for the UPS that is off: battery.charge: 100 battery.charge.low: 15 battery.charge.warning: 50 battery.date: 2001/09/25

On 08/05/2016 03:03 PM, Marco Walther wrote: > On 08/05/2016 01:36 PM, Stuart D. Gathman wrote: >> On Fri, 5 Aug 2016, Marco Walther wrote: >> >>> On 08/03/2016 05:25 AM, Stuart Gathman wrote: >>>> I've made some progress getting this Tripplite to work: >>>> http://gathman.org/2016/07/30/Standard_Schmandard/ >>>> >>>>

On Mon, 3 Apr 2017, Gene Heskett wrote: >>> Nut, IIRC, can do a periodic battery test by putting it offline, >>> using the battery, for a predetermined length of time, weekly, >>> monthly etc, >> >> We definitely don't want that in this instance either! > > Why not? If the battery has a holdup time of 5 minutes when its fresh, Because in this

I and several other users have encountered problems using PowerCOM UPS of the BNT 1500A model. Looking over other responses and dealing with my own issues, I submit the following attached patch. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20110428/00d7d2f9/attachment.htm> -------------- next

Thanks, Charles. I pulled your change and it fixed my segmentation fault. I discovered the following code at line 571 in usbhid-ups.c. This is part of the "checking for alternatives" code: if (!strcasecmp(cmdname, "shutdown.return")) { int ret; /* Ensure "ups.start.auto" is set to "yes", if supported */ if

On 5/28/19 3:39 PM, Julian H. Stacey wrote: > grumpy at mailfence.com wrote: >> a friend gave me an old apc smart-ups 1250 >> it has a rs232 interface but i have no pc with a rs232 port >> i attempted to use a rs232 to usb adapter but the ups goes nuts >> i connected the ups to batteries and verified it was working properly >> when i plug the usb cable into the pc

On Mon, 6 May 2019, Gareth Davies wrote: > Just to say, I stopped the driver and started it again and the errors went > away! However, I turned off power to the UPS but I wasn’t receiving any > e-mails :( also when I rebooted the RPi the driver/service didn’t start back > up automatically...  > > I wonder if you have any thoughts on the above? Those are issues with