similar to: building trunk

Model: Tripp-lite OMNIVS1500 Error: Network UPS Tools - UPS driver controller 2.2.1- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: unknown/unknown libusb_set_report() returned -1 instead of 8 Could not reset watchdog. Please send model information to nut-upsdev mailing

- Charles > On Oct 16, 2016, at 3:34 AM, Daniel Shields <grungelizard9 at hotmail.com> wrote: > > I've been testing with debug further and there's a few extra lines when the nut-server stops communicating as opposed to when it's running. > > > Backtrace after stale data, UPS nailbunny at localhost is unavailable: > Sorry to take a while to get back to you

Hi, Charles I'm trying compilation but there is no configure command in the cloned git directory of nut. D?a 08.10.2017 o 23:47 Charles Lepple nap?sal(a): > On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: >> Thank You for You reply, Charles >> >> >> D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): >>> Is the "lan4.1" cable different

Thank You for You reply, Charles D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): > Is the "lan4.1" cable different from this one? > http://networkupstools.org/cables.html#_tripp_lite Yes, it is different. The correct cable for this interface version looks like this: http://pinouts.ru/UPS/tripplite_smartpro_cable_pinout.shtml > Are you comfortable with rebuilding the

Hi Arnaud & Charles, You?ll have to forgive my low level of Linux Understanding here?. I downloaded the source files, modified the appropriate driver file, re-compiled it (all of this was a lot of research and learning!) When I use the new driver I get ? Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.93 (2.7.4.1) Can't chdir to

Hi Charles, I've been monitoring for the past few days and NUT has been running solid. Tested and everything's working as it should. Thanks for all of your help on this, great to have it running well again and learned lot. ________________________________ From: Daniel Shields <grungelizard9 at hotmail.com> Sent: Tuesday, October 25, 2016 8:01 PM To: Charles Lepple Subject:

Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying

Hello, I've a test system with postfix (SMTP), dovecot (IMAP only) and covecot-LDA (MDA) under FreeBSD-6.1. Currently everything works fine. But I wasn't able to install dovecot-sieve from the CVS. Does anyone has a small documentation howto install dovecot-sieve on FreeBSD. Thanks. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal f?r Modem und ISDN:

Hi, Just started using NUT with a Liebert PSI-XR 3000 with an Intellislot web card. It seems I can't get it to run properly. I am using NUT 2.6.0 built from source on Ubuntu 8.0.4 . My build parameters are : ./configure --enable-strip --with-linux-hiddev=/usr/include/linux/hiddev.h --with-udev-dir=/lib/udev \ --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \

Dear Arnaud, > guys, > > sorry for the lag in jumping over there. > You anyway do a good job! Thanks for prompt answers! > > If you want to do it yourself: > - look here for the needed build tools > http://www.debian.org/doc/maint-guide/ch-start.en.html#s-needprogs > - svn co svn://svn.debian.org/nut/trunk > - cd trunk > - ln -s packaging/debian > - fakeroot

On Sat, Mar 11, 2017 at 7:15 PM, David Baker <david at baker.im> wrote: > Hi Arnaud & Charles, > > > > You?ll have to forgive my low level of Linux Understanding here?. > > > > I downloaded the source files, modified the appropriate driver file, > re-compiled it (all of this was a lot of research and learning!) > > > > When I use the new driver I

On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: > > Thank You for You reply, Charles > > > D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): >> Is the "lan4.1" cable different from this one? http://networkupstools.org/cables.html#_tripp_lite > > Yes, it is different. The correct cable for this interface version looks like this: >

El 18/07/15 a les 17:03, Charles Lepple ha escrit: > On Jul 17, 2015, at 9:42 AM, dmanye <dmanye at urv.cat> wrote: > >> so i reinstalled again... but instead of using four separate partitions for /, /usr, /var and /tmp, put all the stuff under an unique / partition and... it works! why exactly? no idea, because if i'm not wrong, nut sensitive stuff is under /lib, /sbin,

sending to the list for posterity. > On Oct 27, 2016, at 6:43 AM, Raymond Day wrote: > > Thank you. > > Looked like that worked. > > I put your code in /etc/nut/nut.conf just at the end of that file. > > Then did. > > upsdrvctl start > > upsc serverups > > Got this date back: > > battery.charge: 100 > battery.charge.low: 10 >

I see, so you kept the load.on.delay command but removed the check to see if it was handled. Did you do the same thing for the shutdown.stayoff logic? https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L562 This might be a dumb question but did this require you to recompile the kernel? These types of changes are way beyond my depth. Thank you for the direction! On Thu, Jan

My apologies, I forgot a step. See below. > On Oct 9, 2017, at 1:59 PM, tuharsky at misbb.sk wrote: > > Hi, Charles > > I'm trying compilation but there is no configure command in the cloned git directory of nut. > > > D?a 08.10.2017 o 23:47 Charles Lepple nap?sal(a): >> On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: >>> Thank You for You

2017-03-12 4:02 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Sat, Mar 11, 2017 at 7:15 PM, David Baker <david at baker.im> wrote: > > Hi Arnaud & Charles, > > > Hi Dave, any news on your side from this venerable ESV+? -- Arno > You?ll have to forgive my low level of Linux Understanding here?. > > > > > > > > I downloaded

Hi, I'm trying to build nut version 2.0.3 on a RHEL43 rebuild (Scientific LINUX 43). While trying to configure the package I get the following error: ]$ ./configure --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc/nut --with-statepath=/var/nut --with-drvpath=/usr/sbin --with-cgipath=/var/www/cgi-bin --with-cgi --with-user=nutmon --with-group=nutmon --mandir=/usr/share/man

Your suggestion of rebuilding the driver fixed the issue of the UPS turning back during a power failure. Now the UPS shuts down the clients, then powers off appropriately. If power returns it turns back on also. The only bug is if power returns before the UPS has turned the load off. In that case the UPS will remain off until it is manually turned on. This might just be a limitation of this

[As posted as Ubuntu Question #184284 on Launchpad] Hi, I try to set up nut (2.4.3) on my Lucid (10.04.3 LTS) to make use of my old but very trusty UPS (Best Power Fortress 660 LI). Yes, this UPS is old (about 16 years), but with its third battery pack last week it is as good as new. It runs perfectly well with Windows XP, Vista and even Windows 7. But not so with Ubuntu and nut. After