search for: path

...e and after fixing it). Note that after the places marked ###, the parser shifts all Usages by one, which mangles the tree. This bug is fixed in nut-cvs-patch-PARSER-2005-08-24. ---------------------------------------------------------------------- Before fixing the HIDParser bug: HIDDumpTree... Path: UPS.PowerSummary.iSerialNumber Path: UPS.PowerSummary.iDeviceChemistry Path: UPS.PowerSummary.iOEMInformation Path: UPS.PowerSummary.Rechargeable Path: UPS.PowerSummary.APCStatusFlag Path: UPS.PowerSummary.APCStatusFlag Path: UPS.PowerSummary.ManufacturerDate Path: UPS.PowerSummary.ConfigVoltage P...

...yes msdfs proxy = \timmy\tutorials [snr] msdfs root = yes msdfs proxy = \thoth\snr exports.hosts.conf # # This file is autogenerated, so don't bother editing it. # Last generated by /home/tssrc/scripts/cron_scripts/update_hosts_shares.pl # on Mon Aug 15 14:36:27 2005 [aero2k] path = /etc/samba/msdfs_links/hosts/aero2k msdfs root = yes [aggravator] path = /etc/samba/msdfs_links/hosts/aggravator msdfs root = yes [amiga2k] path = /etc/samba/msdfs_links/hosts/amiga2k msdfs root = yes [anise] path = /etc/samba/msdfs_links/hosts/anise msdfs root = yes [...

...UPS Tools: > 0.28 > > USB communication driver 0.28 - core 0.30 (2.1.0) > > > > Report Descriptor size = 1040 > > Detected a UPS: American Power Conversion/Smart-UPS 1500 RM > > FW:617.3.I > > > USB FW:1.5 Using subdriver: APC/CyberPower HID 0.9 > > Path: UPS.PowerSummary.iProduct, Type: Feature, Value: 1.000000 > > Path: UPS.PowerSummary.iSerialNumber, Type: Feature, Value: 2.000000 > > Path: UPS.PowerSummary.iManufacturer, Type: Feature, Value: 3.000000 > > Path: UPS.PowerSummary.iOEMInformation, Type: Feature, Value: > >...

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

...elease number: 0090 > 0.011822 Trying to match device > 0.012248 Device matches > 0.013822 HID descriptor length 1134 > 0.016761 Report Descriptor size = 1134 > 0.019750 Using subdriver: APC HID 0.96 > 0.019824 112 HID objects found > 0.020801 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 2 > 0.021529 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8, Value: 3 > 0.022404 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x03, Off...

Hi Peter, I got all your patches and applied them, and I wanted to say kudos for a great job done. This is the output of upsc that I'm getting right now. I had the same issue when using any cvs version (from two weeks ago) that made my UPS go into a state where it wasn't functioning normally (checking the kernel log shows that it cannot be connected and I had around a page of DEVFS_USB

...314 - Device release number: 0009 0.017430 Trying to match device 0.017736 Device matches 0.021374 HID descriptor length 662 0.111731 Report Descriptor size = 662 0.113247 Using subdriver: TrippLite HID 0.82 0.113406 74 HID objects found 0.115493 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x28, Offset: 0, Size: 8, Value: 2 0.117475 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x29, Offset: 0, Size: 8, Value: 3 0.119478 Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x2b, Offset: 0, S...

...:818.w1.D USB FW:w1 - Serial Number: QB0518132135 HID descriptor retrieved (Reportlen = 872) Report descriptor retrieved (Reportlen = 872) found 1 (872) Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2) Report Descriptor size = 872 Detected an UPS: APC/Back-UPS ES 650 FW:818.w1.D USB FW:w1 Path: UPS.PowerSummary.iSerialNumber Path: UPS.PowerSummary.iDeviceChemistry Path: UPS.PowerSummary.iOEMInformation Path: UPS.PowerSummary.Rechargeable Path: UPS.PowerSummary.APCStatusFlag Path: UPS.PowerSummary.APCStatusFlag Path: UPS.PowerSummary.ManufacturerDate Path: UPS.PowerSummary.ConfigVoltage P...

...HV UPS 0.413805 - Serial Number: 23F1894 0.415214 - Bus: 001 0.416627 Trying to match device 0.418129 Device matches 0.463723 HID descriptor length 1633 3.290756 Report Descriptor size = 1633 3.296583 Using subdriver: EXPLORE HID 0.1 3.323850 Path: UPS.BatterySystem.Battery.BatteryID, Type: Feature, ReportID: 0x20, Offset: 0, Size: 8, Value: 1 3.351148 Path: UPS.BatterySystem.Battery.ffff0090, Type: Feature, ReportID: 0x21, Offset: 0, Size: 8, Value: 0 3.384713 Path: UPS.BatterySystem.Battery.DesignCapacity, Type: Feature, Repo...

...047 0.275063 - Bus: 002 0.275065 - Device release number: 0100 0.275068 Trying to match device 0.275102 Device matches 0.309531 HID descriptor length 2580 4.749244 Report Descriptor size = 2580 4.749684 Using subdriver: MGE HID 1.39 4.749691 234 HID objects found 4.778444 Path: UPS.BatterySystem.Battery.AudibleAlarmControl, Type: Feature, ReportID: 0x28, Offset: 0, Size: 8, Value: 2 4.816700 Path: UPS.BatterySystem.Battery.BatteryID, Type: Feature, ReportID: 0x20, Offset: 0, Size: 8, Value: 1 4.850696 Path: UPS.BatterySystem.Battery.Count, Type: Feature, ReportID:...

> On Sat, 20 Dec, at 12:48:18AM, Ady wrote: > > > > So, my first (still incomplete and still inaccurate) attempt to write > > some rules about the PATH directive, and ask about remaining doubts!... > > > > > > The search (for c32 files) is supposed to respect the following rules: > > > > 1_ The search for c32 files is performed according to the following > > rules. The search for each required c32 file is st...

...gt;> 0.011822 Trying to match device >> 0.012248 Device matches >> 0.013822 HID descriptor length 1134 >> 0.016761 Report Descriptor size = 1134 >> 0.019750 Using subdriver: APC HID 0.96 >> 0.019824 112 HID objects found >> 0.020801 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 2 >> 0.021529 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8, Value: 3 >> 0.022404 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x0...

> On Thu, 18 Dec, at 07:47:18PM, Ady wrote: > > I have a question about the PATH directive. In fact, the question is > > not about how it is currently working, but about its intention or goal, > > or how it was supposed to work (or how it was thought about for the > > 5.00 release). > > > > Previous discussions about the PATH directive in the S...

...al Number: unknown 0.037024 - Bus: 001 0.037027 Trying to match device 0.037042 Device matches 0.037886 HID descriptor too short (expected 8, got 0) 0.037901 HID descriptor length 613 0.057332 Report Descriptor size = 613 0.057663 Using subdriver: TrippLite HID 0.81 0.058304 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x28, Offset: 0, Size: 8, Value: 2 0.059008 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x29, Offset: 0, Size: 8, Value: 3 0.059619 Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x2b, Offset: 0, Size: 8,...

...229 0.770045 - Bus: 006 0.770048 - Device release number: 0100 0.770052 Trying to match device 0.770060 Device matches 0.837058 HID descriptor length 1145 4.506000 Report Descriptor size = 1145 4.506299 Using subdriver: MGE HID 1.39 4.506313 118 HID objects found 4.549980 Path: UPS.BatterySystem.Battery.AudibleAlarmControl, Type: Feature, ReportID: 0x20, Offset: 0, Size: 8, Value: 2 4.601977 Path: UPS.BatterySystem.Charger.PresentStatus.VoltageTooHigh, Type: Feature, ReportID: 0x03, Offset: 0, Size: 8, Value: 0 4.601994 Path: UPS.BatterySystem.Charger.PresentStatus...

...- Bus: 003 Trying to match device Device matches failed to claim USB device, trying 2 more time(s)... detaching kernel driver from USB device... trying again to claim USB device... HID descriptor length 1004 Report Descriptor size = 1004 Using subdriver: TrippLite HID 0.2 (experimental) Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x28, Offset: 0, Size: 8, Value: 6.000000 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x29, Offset: 0, Size: 8, Value: 20.000000 Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x2b, Offset: 0, Size: 8, Value: 4....

On Tue, 11 Jun, at 03:54:21AM, H. Peter Anvin wrote: > On 06/11/2013 01:03 AM, Matt Fleming wrote: > > On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: > >> Either that or make the path a list rather than a string, using the > >> normal word separators when entered on the command line, a bit like the > >> (t)csh does. That is a bigger change but is probably a better solution. > > > > How would this solution handle filenames containing spaces? Would...

...ks!. Now looks better, but still not work. > > For some reason, "ldlinux.c32" is apparently sent but "Failed to load" > by PXELINUX and few seconds later, dnsmasq shows an error message > "failed sending": Argh! The patch was broken. I missed the new core/path.c file. My bad. I'll resend. -- Matt Fleming, Intel Open Source Technology Center

Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Now I'm back to another issue, every 2 seconds I get in the logs: May 3 13:45:23 myhost upsd[2587]: Connected to UPS [eaton]: usbhid-ups-eaton It seems happy to do this forever. On Tue, May 3, 2016 at 8:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On

On Sat, 20 Dec, at 12:48:18AM, Ady wrote: > > So, my first (still incomplete and still inaccurate) attempt to write > some rules about the PATH directive, and ask about remaining doubts!... > > > The search (for c32 files) is supposed to respect the following rules: > > 1_ The search for c32 files is performed according to the following > rules. The search for each required c32 file is stopped once the first > mat...