Nut upsuser - May 2007 - [Nut-upsdev] Belkin USB UPSes

OK Eric,
Den Tuesday 22 May 2007 08.56.08 skrev Eric S. Raymond:
> Kjell Claesson <kjell.claesson at epost.tidanet.se>:
> > Or install the udev rules and replug the ups.
>
> Did that.  Manual startup of the driver now works without -u root,
> indicating (I think) that the udev rools are doing their job.  This
>
8<-----------------------Snip----------------------------------------
> /proc/bus/usb/002:
> total 0
> crw-rw-r-- 1 root root 189, 128 2007-05-18 01:47 001
> crw-rw-r-- 1 root nut  189, 130 2007-05-22 02:46 003
>
> /proc/bus/usb/003:
> total 0
> crw-rw-r-- 1 root root 189, 256 2007-05-22 02:44 001
>
> also indicates that permissions look OK.
>
> However, starting with upsdrvctrl still reports driver startup failing
> with exit 1.  What other things besides permissions errors can cause this?
>
Normaly it should say something more than 'exit 1'.

Did You install from svn ?

And if so, did You set the state_path during configure. You may be
missing or having the wrong rights on that directory.
Default it should be /var/state/nut/.

This directory holds the driver socket, and if it don't exist it
would make the upsdrvctrl exit with a error.
> (I plan to submit a patch for the installation instructions  if we
> can figure this out, so your advice will benefit the next person to
> trip over this, too.)
Take care that there is difference depending on udev version and libusb.

As ther was changes around the access to /proc in the kernel, this is
changed in the udev. So now it makes devices under /dev/bus/usb/xxx

And for libusb,
Quote:
* Fri Jan 27 2006 Jindrich Novy <jnovy at redhat.com> 0.1.11-2
- change device search order, /dev/bus/usb is tried first,
  then /proc/bus/usb, and never try /sys/bus/usb (#178994)
Unquote

This was released in libusb 0.1.12 so now the device is
/dev/bus/usb/00x/00x

The /proc/bus/usb/xxx/xxx is setup to belong to root:usb now.

Regards
Kjell

P.S. Peter Selinger made me change mail client. Didn't notice that it was
not
cc'd to the list.

Kjell Claesson <kjell.claesson at
epost.tidanet.se>:
> Normaly it should say something more than 'exit 1'.
Yes, I think so.  That's part of my issue here I don't want to just 
solve the problem, I want to make the diagnostic messages better so
nobody has to be as confused as I am.
 
> Did You install from svn ?
Yes.
> And if so, did You set the state_path during configure. You may be
> missing or having the wrong rights on that directory.
> Default it should be /var/state/nut/.
esr at snark:~$ ls -ld /var/state/ups/
drwxr-xr-x 2 nut nut 4096 2007-05-22 12:46 /var/state/ups/
> This directory holds the driver socket, and if it don't exist it
> would make the upsdrvctrl exit with a error.
So, in that case shouldn't upsdrvctl emit a message more like "driver
socket
nonexistent or inaccessible -- please check /var/state/nut/"?  If not,
why not?
> > (I plan to submit a patch for the installation instructions  if we
> > can figure this out, so your advice will benefit the next person to
> > trip over this, too.)
> 
> Take care that there is difference depending on udev version and libusb.
> 
> As ther was changes around the access to /proc in the kernel, this is
> changed in the udev. So now it makes devices under /dev/bus/usb/xxx
> 
> And for libusb,
> Quote:
> * Fri Jan 27 2006 Jindrich Novy <jnovy at redhat.com> 0.1.11-2
> - change device search order, /dev/bus/usb is tried first,
>   then /proc/bus/usb, and never try /sys/bus/usb (#178994)
> Unquote
> 
> This was released in libusb 0.1.12 so now the device is
> /dev/bus/usb/00x/00x
> 
> The /proc/bus/usb/xxx/xxx is setup to belong to root:usb now.
OK, what do I *do* with this information?  What should go in the
installation instructions?
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>