similar to: [PATCH] udev rules for APC 5G

I've grabbed a snapshot of NUT from just a couple days ago. Glad to see APC's new 5G UPSes added to the list (though you probably want to add it to the UDEV 52-nut-usbups.rules file as well...). My issues with new APC Smart-UPS units (SMT1000) : Powering-down the unit, whether with upsdrvctl or upscmd will not obey the specified delay in offdelay, or ups.delay.shutdown. Instead, a

Hi Guys, I'd like to submit a patch to enable NUT to communicate with APC 5G UPSs. The current usbhid-ups driver recognises APC UPSs by the Vendor ID and Product ID of 0x051D and 0x0002. This needs to be amended with the new Product ID of 0x0003. (See attached file: apc-hid.patch) Secondly, when Nut polls the UPS via the interrupt channel, these will time out, resulting in frequent lost

I need direction. I don't know what to google for anymore. I am unable to get my SmartUPS 2200XL to be recognized. My suspicions are that it's UDEV or Kernel related. I've updated the kernel to the highest version I feel comfortable with due to other things that run on the server, and I've updated UDEV a bit too. When I plug in the USB cable from the UPS into the server, I

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

Thought I would write some notes about how I got an APC BackUPS XS 1500 working with newhidups under Gentoo 2006.0. The specific issue here is the permissions on the device files used that libusb uses to access the USB hardware. I followed Peter Selinger's instructions at http://www.mscs.dal.ca/~selinger/ups/backups.html on getting newhidups going with an APC device. The sticking point for

Hi. Is the subject UPS model supported? I believe so, but I don't have a unit to test with. Any comments on this model? I'm trying to advise a colleague. Thank you, as always. T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=051d ProdID=0003 Rev= 1.06 S: Manufacturer=American Power

Hi all, just installed the nut package from apt on Ubuntu. Here's what I got. Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 This APC device (051d:0003) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the

Package: xen-utils-common Version: 4.0.0-1 Severity: normal A strange issue, when deploying Xen using Puppet, /etc/udev/rules.d/xend.rules and /etc/udev/rules.d/xen-backend.rules files are empty. Specifically, the symlinks point to ../xend.rules and ../xen-backend.rules respectively in /etc/udev, but neither of those files exist. Manually copying those files from another host that was not

I have a machine running 4.1 did hte update to 4.2 my zaptel settings (asterisk pbx) seemed to have gotten lost in the update. The file was /etc/udev/rules.d/50-udev.rules Jerry

Package: xen-utils-common Version: 3.0.3-0-1 Severity: serious Justification: makes package uninstallable Usertags: grid5000 Hi, During a piuparts run over all the packages in etch, I ran into a problem with your package: Setting up xen-utils-common (3.0.3-0-1) ... ln: creating symbolic link `/etc/udev/rules.d/z60_xen-backend.rules' to `../xen-backend.rules': No such file or directory

Does anyone else have any thoughts on automatically installing the udev rules file to avoid all of the "can't find UPS" errors? If we make this a ./configure parameter, we can check for the existence of the udev binary, and allow customization of the rule file name (for adjusting the number prefix). I still think it can't hurt to expand the USB driver error messages a bit (if

Hi, seems there is one missing change in /trunk/scripts/udev/nut-usbups.rules.in BUS -> SUBSYSTEMS previous change [1] missed this. Now, the latest udev started to complain: > ... udevd[31526]: BUS= will be removed in a future udev version ... 098 udev version (from 2006) is required for this [2], but this is the same version as required for previous SYSFS -> ATTR change. I've

>On Thu, 2005-10-20 at 07:53 -0500, Jerry Geis wrote: >>/ I have a machine running 4.1 did hte update to 4.2 />>/ my zaptel settings (asterisk pbx) seemed to have gotten lost />>/ in the update. The file was /etc/udev/rules.d/50-udev.rules />>/ />---- ?that is why you are supposed to not make changes to that file but rather >put any changes/new entries in

I am migrating from Fedora 8 to CentOS 5.2 I have usb dvd On F8 I have /etc/udev/rules/00-my-custom.rules BUS=="scsi", SYSFS{vendor}=="TSSTcorp", SYSFS{model}=="CDDVDW SH-S203N ",SYMLINK="dvd",OWNER="rray" When I plug in dvd I get $ ll /dev/scd1 lrwxrwxrwx 1 root root 3 Aug 25 08:17 /dev/scd1 -> sr1 ll /dev/sr1 brw-r----- 1 rray disk 11, 1

Il 07/08/2014 15:09, Amit Shah ha scritto: > +udevrules_DATA = 90-virtio-rng.rules If rng-tools is packaged with "make dist" you need this to be dist_udevrules_DATA = 90-virtio-rng.rules or alternatively EXTRA_DIST = 90-virtio-rng.rules udevrules_DATA = 90-virtio-rng.rules > +AC_ARG_WITH([udevrulesdir], > + AS_HELP_STRING([--with-udevrulesdir=DIR], [Directory for udev

Il 07/08/2014 15:09, Amit Shah ha scritto: > +udevrules_DATA = 90-virtio-rng.rules If rng-tools is packaged with "make dist" you need this to be dist_udevrules_DATA = 90-virtio-rng.rules or alternatively EXTRA_DIST = 90-virtio-rng.rules udevrules_DATA = 90-virtio-rng.rules > +AC_ARG_WITH([udevrulesdir], > + AS_HELP_STRING([--with-udevrulesdir=DIR], [Directory for udev

I'm trying to work out how to set up a custom udev rule to override permissions on serial ports (/dev/ttyS* and /dev/ttyUSB*) on CentOS 5.3 The default rule, in /etc/udev/rules.d/50-udev.rules has the line: KERNEL=="tty[A-Z]*", NAME="%k", GROUP="uucp", MODE="0660" and I would like the mode to be 0666 Various docs on web say that you

Hi, I would like to change permissions of /dev/sda* and /dev/hda* files to 0644. I added the following rules to 99-udev.rules files: KERNEL=="[hs]d*", OWNER="root" GROUP="disk", MODE="0644 After restarting udev by strat_udev, I checked that permissions were changed: [root at gini rules.d]# ll /dev/sda* brw-r--r-- 1 root disk 8, 0 Sep 2 2009 /dev/sda

Hi Pawel, 2011/7/26 Pawel Sikora <pluto at agmk.net> > On Tuesday 26 of July 2011 14:33:15 you wrote: > > Hi Pawel, > > > > 2011/7/26 Pawel Sikora <pluto at agmk.net> > > > > > Hi, > > > > > > i have an orvaldi ups > > > http://en.orvaldi.com/index.php/en/product_catalog/product_view/11/162 > > > and it works