similar to: Powercool PCRACK-1200VA patch update

Hi Folks, This is my first post on nut-upsdev. I would like to share a small patch to enable support for the Powercool PCRACK 1200VA ups. I found that the UPS uses megatec/krauler protocol but is sensitive to the USB buffer length passed to it in requests via usb_get_string(), and usb_get_string_simple(). If the buflen is greater than 102 then the ups will reply to requests but does not

I think having this logic buried within libhid/libusb (libusb:libusb_open(), line 179 to 206) is ultimately a mistake, albeit one that I am probably responsible for. Would it make sense to confine libhid to low-level operations, and leave the decision of trying to reopen vs. retrying to open to the high-level driver, in this case usbhid-ups? I envision that the code in usbhid-ups:reconnect_ups()

I get the following error on r809 (but it looks like the code change happened here). Does HIDDevice_t need to be defined/changed in one of the headers? if gcc -DHAVE_CONFIG_H -I. -I../../drivers -I../include -I../../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I.

Hi all, My name is Sergio Penen and I'd like to contribute to the project by developing a new driver for TS SHARA SOHO II usb ups. I'm almost done decoding the protocol and already have some basic functionality working with NUT. However I've some doubts on how to integrate this driver with NUT and I wonder if you could give me some guidance in that sense. To be more specific: In order

I recently installed NUT 2.4.3 and found that the USB drivers were logging an insane amount of data to syslog: usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report: No error usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report: No error usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report: No error usbhid-ups | daemon debug | Apr 16 18:29:40 |

On Dec 17, 2011, at 3:53 AM, Arnaud Quette wrote: > Author: aquette > Date: Sat Dec 17 08:53:41 2011 > New Revision: 3363 > URL: http://trac.networkupstools.org/projects/nut/changeset/3363 > > Log: > Try to fix language ID support for USB units from LDLC, Dynamix and no names in blazer_usb (reworked patch, from Brian R. Smith and Aur?lien Grenotton) ... > + if

> next_device: > + free(curDevice->Vendor); > + free(curDevice->Product); > + free(curDevice->Serial); > + free(curDevice->Bus); > usb_close(udev); > udev = NULL; > } Wouldn't it be necessary to check whether there is anything to free or not? Vendor, Product and Serial are set conditionally. In the lines upsdebugx(2, "-

I doesn't fix any problems but I think it is nicer code. :-) I don't think we want to call usb_detach_kernel_driver_np unless we claimed the device. $ diff -uw libusb.c.bak libusb.c.new --- libusb.c.bak 2010-05-11 09:35:39.000000000 -0400 +++ libusb.c.new 2010-05-11 09:32:44.000000000 -0400 @@ -206,18 +206,21 @@ upsdebugx(2, "failed to

Hi, (please let me know if there is a better place to submit bugs) I run a FreeBSD box with stack-protector enabled, which raises a problem in the upsdrv_initups() function of the newhidups.c module; the regex_array variable is sized one item too small. Regards, Herve Masson <<<< void upsdrv_initups(void) { int i; #ifndef SHUT_MODE /*! * SHUT is only supported by

Strict C99 compilers do not support implicit function declarations or implicit ints, so something like the patch below is needed. Thanks, Florian diff --git a/configure.ac b/configure.ac index 4f68e98a..b5c7a582 100644 --- a/configure.ac +++ b/configure.ac @@ -173,6 +173,9 @@ AC_RUN_IFELSE([AC_LANG_SOURCE([[ #include <fcntl.h> #include <sys/types.h> #include <sys/wait.h>

In the past there have been discussions about adding a switch to rsync to preserve the atime on files being copied by rsync. I needed this function for a project I'm working on and decided to invent it. I've attached the diffs. Note that this has the limitations describe in previous emails, namely that preserving atime causes ctime to not be preserved. *** Patch follows *** ***

------- start of forwarded message (RFC 934 encapsulation) ------- From: Joe Zbiciak <im14u2c@cegt201.bradley.edu> Approved: alex@bach.cis.temple.edu Sender: Bugtraq List <BUGTRAQ@netspace.org> To: Multiple recipients of list BUGTRAQ <BUGTRAQ@netspace.org> Subject: Buffer overflow in Linux''s login program Date: Sun, 22 Dec 1996 09:27:24 -0600 Reply-To: Joe Zbiciak

I have successfully connected UPS RUCELF UPI-1000-12-EL to NUT, and would like to contribute .dev file for this model to NUT's Devices Dumps Library. file is attached to the mail, I also added a copy below: # --- Rucelf__UPI-1000-12-EL__blazer_usb__2.7.4__01.dev -- battery.charge: 100 battery.packs: 6 #COMMENT: added manually to fix battery.voltage (was: 2.22), see ups.conf below

Hi to everyone! I'm posting here after digging around the nut-upsuser and nut-upsdev mailing list, hoping I didn't miss something important. I'm trying to make my ups working with nut: it's a Tecnoware ERA LCD 0.85 which uses the so-hated UPSilon 2000 software to connect via usb. Personally I checked and seems that this junk software only works from windows, I'm trying to

Hi. Here's a patch for copying the atimes of files when -t/--times is given. I bumped the protocol to 29 since it sends more data over the wire. It obviously does not send the atime if it's sending data to an older rsync version. It passes all the tests (including the added atime.test) for me on a: Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system. Any questions/feedback? I

Dear Martin Pool. We regularly use rsync for making backups of our file systems but we have noticed that the atimes are not transferred with the files and are also always updated on the sender's side. Therefore, we have created a modified version of rsync based on rsync-2.6.6 protocol version 29 which transfers the access times with the transferred files and also allows to preserve the access

Hello, I am encountering a linking failure when using Control Flow Integrity while building a shared library. It looks like the wrong relocation type is being emitted for functions referenced via the PLT. I am using clang 3.9. The error message I get is: /usr/bin/ld.gold: error: /tmp/lto-llvm-df723d.o: requires dynamic R_X86_64_PC32 reloc against 'free' which may overflow at runtime;

Atlantis Land A03-P551(V1.2) battery.charge: 100 battery.voltage: 13.70 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.mfr: device.model: device.type: ups driver.name: blazer_usb driver.parameter.langid_fix: 0x0409 driver.parameter.pollinterval: 2 driver.parameter.port: x driver.version: 2.6.4 driver.version.internal: 0.08 input.current.nominal: 0.0

From: Jason Gunthorpe <jgg at mellanox.com> This converts one of the two users of mmu_notifiers to use the new API. The conversion is fairly straightforward, however the existing use of notifiers here seems to be racey. Tested-by: Dennis Dalessandro <dennis.dalessandro at intel.com> Signed-off-by: Jason Gunthorpe <jgg at mellanox.com> --- drivers/infiniband/hw/hfi1/file_ops.c

I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?