search for: urbnum

On Dec 14, 2013, at 4:23 PM, David C. Rankin wrote: > Do you know if the problem with upsdrvctl being able to probe/connect to the > usb devices is the result of some default permission change in Linux in general. > It seems to me that since nut used to work right out-of-the-box, then all/most > distros must have had the default permissions on usb nodes set to 0666, where >

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

...an be composed by the attributes of the device and the attributes from one single parent device. The group of ATTRS that look promising are: looking at device '/devices/pci0000:00/0000:00:04.0/usb4/4-3': ATTR{idVendor}=="0764" ATTR{bcdDevice}=="0001" ATTR{urbnum}=="161297" ATTR{manufacturer}=="CPS" ATTR{idProduct}=="0501" ATTR{bDeviceClass}=="00" ATTR{product}=="UPS CP1000AVRLCD" looking at parent device '/devices/pci0000:00/0000:00:04.0/usb4': ATTRS{idVendor}=="1d6b&quot...

...KERNEL=="4-2" SUBSYSTEM=="usb" DRIVER=="usb" ATTR{configuration}=="1" ATTR{bNumInterfaces}==" 1" ATTR{bConfigurationValue}=="1" ATTR{bmAttributes}=="e0" ATTR{bMaxPower}==" 30mA" ATTR{urbnum}=="3668" ATTR{idVendor}=="051d" ATTR{idProduct}=="0002" ATTR{bcdDevice}=="0006" ATTR{bDeviceClass}=="00" ATTR{bDeviceSubClass}=="00" ATTR{bDeviceProtocol}=="00" ATTR{bNumConfigurations}=="1"...