similar to: nut for wisp-dist

i've got a nut.lrp package now for GLIBC-2.2 on wisp-dist 1.3 (linux-2.4.25), if someone is interested of. Michael Plourde Digicom Technologies Inc.

Hi, i'm trying to compile nut for a wisp-dist (linux for router) but i have problem with glibc. Wisp-dist using linux 2.4.25 with glibc-2.2 and most of the nut-2.0.0 use glibc-2.3 librairy, i think. Is there a version that is compatible with GLIBC-2.2. Michael Plourde

Hi, What driver should i use with APC BK-300C ? Michale Plourde Digicom Technologies

Hi, i had purchase a MGE-Ellipse 500 and i'm trying to use the DB9 F / RJ45 cable send by MGE with UPS. Which driver i'm suppose to use: mge-utalk or mge-shut ? When i try mge-utalk i've got this message: # upsdrvctl start Network UPS Tools - UPS driver controller 2.0.0 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.80.3 (2.0.0) Startup timer elapsed, continuing... and there is

[BackUPS] driver = apcsmart port = /dev/ttyS0 desc "Back-UPS BK-300 @ Cap a l'orignal" > ----- Original Message ----- > From: "Charles Lepple" <clepple@gmail.com> > To: "NUT-MList" <nut-upsdev@lists.alioth.debian.org> > Sent: Monday, June 19, 2006 2:38 PM > Subject: Re: [Nut-upsdev] Backups 300VA (BK-300C) Drivers >

Dear R-Team! I am a beginner in R and use the WISP library for a project. I am using mark-recapture to estimate abundance. I would like to know if it is possible to only survey a part of the created area (with the created population) and not all of it. I am trying to quantify bias introduced by non random sampling design (i.e. the area is 24x100 but I only wanna search 24x40) Thank you already in

On Apr 8, 2015, at 2:04 PM, Eric Cobb <Eric_Cobb at tripplite.com> wrote: > Charles and list, > > If I leave the driver alone it does not eventually start. It continues to report that it is unable to connect. I have to perform a upsdrvctl stop ; upsdrvctl start (I actually just perform a init stop and start so that upsd and upsmon both restart) for the driver to actually

Hi, I've found that upsdrvctl crashes when there is not ports= specified ups.conf #0 __strrchr_sse2 () at ../sysdeps/x86_64/strrchr.S:33 #1 xbasename (file=0x0) at common.c:266 #2 stop_driver (ups=0x1e163e0) at upsdrvctl.c:135 #3 send_all_drivers (command=0x4020f0 <stop_driver>) at upsdrvctl.c:446 #4 main (argc=1, argv=0x7ffff30be9c0) at upsdrvctl.c:565 stop_driver

Hello everyone, Here are the output log files as requested. Eric Cobb ekcobb at tripplite.com From: aquette.dev at gmail.com [mailto:aquette.dev at gmail.com] On Behalf Of Arnaud Quette Sent: Thursday, April 09, 2015 5:03 AM To: Charles Lepple Cc: Eric Cobb; nut-upsdev at lists.alioth.debian.org Subject: Re: [Nut-upsdev] CENTOS 6.6 NUT RPM BUILD ISSUES Hey 2015-04-09 1:46 GMT+02:00 Charles

Hey 2015-04-09 1:46 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Apr 8, 2015, at 2:04 PM, Eric Cobb <Eric_Cobb at tripplite.com> wrote: > > Charles and list, > > If I leave the driver alone it does not eventually start. It continues to > report that it is unable to connect. I have to perform a upsdrvctl stop ; > upsdrvctl start (I actually just perform

Hi, one user found problem with restarting nut. upsdrvctl does not wait for drivers being really terminated. In init scripts we have following: killproc upsmon killproc upsd upsdrvctl stop and then upsdrvctl start upsd upsmon problem is upsdrvctl stop only sends terminating signals but does not wait for driver termination. This makes driver fail to start sometimes when old driver is still

Hi Charles, I'll try the blazer_ser and the nutdrv_qx with version 2.7.1 later. Below, the result of 'lsusb -vvv' requested: Bus 004 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level)

Hi, you've probably heard about systemd already. In Fedora 15, it's used as default instead old SysV init system. While there is some backward compatibility layer, everything is going to be ported from /etc/init.d/<something> init scripts to systemd's service files /lib/systemd/system/<something>.service Unfortunately?, systemd is not 1:1 compatible with old init

> Hello Arnaud, Hi Alex, > First of all i want to thank you for such useful and convenient > system tool as NUT. I think it is one from most important tools > for server machines. And it make its work excellent. thanks > I use NUT on SuSE distro and adapted init-scripts from package for > this distro style. Send you them with hope that you find them useful > for

All, I have built and installed nut from git on Archlinux. It uses the usbhid driver. Beginning a couple of years ago, nut begin failing to run on Archlinux without 'tweaking' or 'fudging' the install. There are two primary problems: (1) upsdrvctl cannot be launched normally i.e. (/usr/sbin/upsdrvctl start) without failing to connect: Dec 14 02:24:39 phoinix systemd[1]:

Has anyone gotten this model of tripp-lite to work? sudo /usr/local/bin/upsdrvctl -DDDDD -u root start Network UPS Tools - UPS driver controller 2.0.5 Starting UPS: tripplite exec: /usr/local/bin/tripplite_usb -a tripplite Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.7 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP

On 12/14/2013 02:06 PM, David C. Rankin wrote: > Charles, > > Setting uid:gid to root:nut on /dev/bus/usb/004/002 seemed to be the issue. > The question now become how to automate this process so that the user isn't > required to manually hunt down the usb dev and change gid to the nut gid? So > far, either manually setting the gid or hand-rolling the udev files to do the

On Mar 23, 2015, at 7:57 PM, Eric Cobb <Eric_Cobb at tripplite.com> wrote: > Number 1 change - 2.7.2 no longer has the HAL scripts that 2.6.5 has. I am working on if HAL is actually required on CentOS6.6 with the 2.7.2 code or if they have another way around it. This is code diving which is taking some time. HAL support in NUT was bit-rotting, so it was removed. It isn't

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what

That worked out just fine. What I am currently running into are conditions where I am getting the following error that I figured I would share. Error: libusb_get_interrupt() returned 0 instead of 8 while sending 3a 4d b2 0d 00 00 00 00 '.M......' Conditions: upsdrvctl start via Init Script at Boottime. If I run the init script after boot, I do not receive this error. Eric Cobb ekcobb