<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Tomas and Arjen<br>
<br>
Thanks for your very expert assistance....<br>
<br>
We are definitely getting close to solving this. Maybe there is a
packaging problem - or maybe there is a problem somewhere else in my
system.<br>
<br>
If I track down the ups usb port - and change the permissions of the
/dev/bus/usb/xxx/yyy as suggested by Tomas - everything works fine -
as far as I can tell so far at least.<br>
<br>
I note though - that in my system - the usb device number seems rather
erratic. Over the past day or so - the usb device number of the UPS has
been increasing (possibly whenever I kill the processes trying to
attach to it??) I am confident that i have not removed the connector or
rebooted the system or powered off the UPS - but the device number
originally reported as 4 and today it was up to 14.<br>
<br>
Today I also tried some experiments where I changed the permissions so
that nut was working - then unplugged the usb cable, then plugged it
back into the same connector. The device number increased from 4 to 5
and I had to fix the permissions again.<br>
<br>
How much of this behaviour is as you would expect?<br>
What do you think caused the device number to increase without me
removing the cable or rebooting?<br>
Is it normal that the number will change when I unplug/replug?<br>
Arjen refered to "hotplugging/udev" scripts. Where should these be? I
wasn't able to find them anywhere - but maybe I am looking for the
wrong thing in the wrong place.<br>
Tomas - Do you know why redhat removed nut from their RHEL? Did they
replace it with something?<br>
<br>
Again thank you both for your help.<br>
<br>
Richard.<br>
<br>
<br>
Tomáš Smetana wrote:
<blockquote
cite="mid:20071126141011.1a8fc88d@dhcp-lab-165.englab.brq.redhat.com"
type="cite">
<pre wrap="">On Mon, 26 Nov 2007 21:36:29 +0900
Richard Chapman <a class="moz-txt-link-rfc2396E" href="mailto:rchapman@aardvark.com.au"><rchapman@aardvark.com.au></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Arjen
Also for Tomas Smetana of the epel repository
I think we are getting somewhere - but not quite to the final goal...
If I run:
/sbin/usbhid-ups -u root -DDDDD -a BelkinUps
as suggested it all works fine - and finds the UPS on the USB port.
It still does so if I remove all the -DDDDDs.
However - if I run it without the -u root - it will not find the UPS.
When I run the provided startup script (action) - it behaves very
much the same as when I run the above command without the "-u root"
option. I am running the script as root (I think). It appears to me
that maybe the script is not running the driver as root for some
reason, or maybe the user it runs as has insufficient rights. I have
had a quick look at the script but it isn't obvious how or where it
runs the driver, so I will need to look further. Does anything
obvious spring to mind as to why the standard startup action may be
starting the driver as the wrong user? As far as I can see - the user
"nut" and/or the group "nut" must have been created by the rpm
install. I didn't knowingly create them. What user would you expect
the driver to run as?
I could attach the action script - but I'm not sure it will help.
</pre>
</blockquote>
<pre wrap=""><!---->
The drivers are supposed to run under user "nut" group "uucp". Your
problem seems to be somewhere in the udev rules provided with the rpm
package -- they should change the ownership and permissions of the
appropriate USB devices. If you have your UPS attached
on /dev/bus/usb/003/002 then ls -l /dev/bus/usb/003/002 should say:
crw-rw---- 1 root uucp 189, 257 2007-11-26 14:05 002
(i.e. mode 0660, group uucp)
I will try to find out what's exacly wrong. But everything points to
the udev rules. Sorry for the inconveniences.
Regards.
</pre>
</blockquote>
<br>
</body>
</html>