similar to: consolidating the NUT documentation on permissions, hotplug and udev

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

Hello all, I am trying to set up my brother's UPS (remotely over internet) on an OpenIndiana-based storage box. According to him, the UPS is probably an Ippon Back Power Pro 600 dated around 2003 (battery recently replaced), and it has an USB connection. Sorry for a relatively long post with a log of my successes and failures, in the hopes that someone would point out what I did wrong.

Hi, Apologies for the many replies. I have found this documentation: http://www.lehman.cuny.edu/cgi-bin/man-cgi?ugen+7 (I am using the ugen driver). Richard On Sun, Apr 5, 2015 at 3:34 AM Richard Flint <richard.flint at gmail.com> wrote: > Hi, > > I have to admit this sounds like it could screw up the system if not done > right - particularly because the solaris packaging

On Sep 23, 2014, at 3:55 AM, Henning Brauer <hb-nut at bsws.de> wrote: > We have upd(4) attaching to these devices now. Either nut needs a > driver getting status from upd (trivial, will show up in the > hw.sensors sysctl tree) or we need some way for nut still being able > to talk to the ups directly, without upd and nut interfering with each > other. While a upd(4) driver

Hi, Unfortunately this approach isn't going to work. I've done some further research and it would appear that it is the underlying ugen device and not libusb that is failing to honor the timeout. https://mail-index.netbsd.org/tech-misc/2006/03/17/0000.html The person above worked around this by having the device opened in non blocking mode using the O_NONBLOCK flag but this required

I've been using nut with a serial device for a while, but today I tried hooking up this new CyberPower 685 unit via newhidups--since it seemed better supported over USB than serial, based on reading the list archives and cvs logs. Unfortunately, I can't connect to it. My system sees the device: uhid1: CPS UPS BF700, rev 1.10/0.01, addr 2, iclass 3/0 ... and I have chmodded all

Hi I have PW 5115 500 UPS which has both RS232 and USB connectors. bcmxcp driver works fine with serial connection but bcmxcp_usb does not with USB one. After some USB sniffing on windows box I've found that PW5115 communicates in other way than supposed in driver. Applying attached patch makes driver to work properly. System: FreeBSD 6.2 but ugen driver needs patching in order to respect

I''m using kubuntu dapper, so /proc/sys/kernel/hotplug is disabled, and instead udevd is running to get events from kernel and do what is necessary. in my first steps with xen (unstable), I get this error: root@nandemonai:~# xm create myxm Using config file "/etc/xen/myxm". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. root@nandemonai:~#

Hi Arjen 2007/7/28, Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Sat Jul 28 16:45:04 2007 > New Revision: 1029 > > Log: > Add Belkin F6C1200-UNV (older model) to supported devices. > > Apparently this is (internally) identical to the F6C1100-UNV. Not surprisingly, they also share the same productid (1100). It also seems to come

2010/12/22 Arjen de Korte <adkorte-guest at alioth.debian.org> > Author: adkorte-guest > Date: Wed Dec 22 20:31:42 2010 > New Revision: 2777 > URL: http://trac.networkupstools.org/projects/nut/changeset/2777 > > Log: > Don't version generated files > > Deleted: > trunk/scripts/hal/ups-nut-device.fdi.in > trunk/scripts/hotplug/libhid.usermap >

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Thu Jan 15 20:02:22 2009 > New Revision: 1734 > > Log: > Freshly generated USB helper files > > Modified: > trunk/scripts/hal/ups-nut-device.fdi.in > trunk/scripts/hotplug/libhid.usermap > trunk/scripts/udev/nut-usbups.rules.in Questions is, should we try

> Added: > trunk/scripts/hotplug/Makefile.am > trunk/scripts/udev/Makefile.am > Modified: > trunk/ChangeLog > trunk/Makefile.am > trunk/configure.in > trunk/docs/configure.txt > trunk/scripts/Makefile.am > trunk/scripts/hotplug/ (props changed) > trunk/scripts/udev/ (props changed) > trunk/scripts/udev/README > Log: > -

Hello, The current dependancy on hotplug|udev (>= 0.59) seems bad. As far as I remember, last week, when I tried to install Ralph packages, I got an error from hotplug/udev and I had to use udev from backports.org Anyone know which version of udev/hotplug we will have to depends on ? Maybe we could simply rely on a recent udev dependancy, because afaik udev now provides hotplug. -- Julien

Citeren Arnaud Quette <aquette.dev at gmail.com>: > Author: aquette > Date: Sat Nov 15 21:50:40 2008 > New Revision: 1556 > > Log: > USB "improved maintenance" code. Refer to docs/new-drivers.txt for > more information... > > Added: > trunk/drivers/usb-common.c > trunk/drivers/usb-common.h > trunk/tools/ > trunk/tools/Makefile.am >

[It seems the last time this came up was in march, under the heading of "Sony Cybershot should be in hardware notes". This message is intended mainly to document what I've managed to track down.] The m500s still will not sync with pilot-link 0.11.7 in -STABLE. An easily triggerable panic is another issue [1]. The pilot-link code first opens /dev/ugenX and then switches to

OpenBSD 6.1/amd64 nut-2.7.4p0 (from OpenBSD package) UPS: Tripp-Lite OMNI1500LCDT I cannot get the driver for the UPS to load without error. Here are the commands, with the output, and the config files: ======================================================= # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication

I made the following devd script.. sh cd /tmp fetch mkdir /usr/local/etc/devd sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\ device-name "ugen[0-9]+";\ match "vendor" "0x\1";\ match "product" "0x\2";\ action "chown @RUN_AS_GROUP@

On Mon, Oct 29, 2007 at 9:45 PM, Daniel O'Connor <doconnor at gsoft.com.au> wrote: > I made the following devd script.. > > sh > cd /tmp > fetch > mkdir /usr/local/etc/devd > sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\ > device-name "ugen[0-9]+";\ > match

* Henning Brauer <hb-nut at bsws.de> [2014-09-20 13:39]: > * Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]: > > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > > Looks like this patch fixed the problem. I see the status change now. > > Good to hear. > > I'm not familiar with the OpenBSD release process. Is

All: I am having a devil of a time getting nut to work on freebsd. Here is what I have done. I am trying to load the drivers, and here is my ups.conf file: [tripplite] driver=trippliteesu port=auto When I dmesg on freebsd 7.1 for my usb device: uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.00, addr 2> on uhub0 using the usbdevs -v command: Controller /dev/usb0: addr 1: