[Nut-upsdev] NUT-2.0.5: newhidups on RedHat ES4

[Patrick Agrain]

Hi Arjen,

I completely agree with you.
And the udev man page is explicit about this point.

I already had this kind of trouble when trying to detect a basic USB memory 
key.

I will have a look at a RH patch.

Thanks.
Regards,

Patrick Agrain

At 20:26 27/03/2007, Arjen de Korte wrote:
>Patrick Agrain wrote:
>
> > udev rules :
> > # MGE UPS SYSTEMS - usbhid-ups
> > SYSFS{idVendor}=="0463", SYSFS{idProduct}=="ffff", MODE="664", GROUP="nut"
> > SYSFS{idVendor}=="0463", SYSFS{idProduct}=="0001", MODE="664", GROUP="nut"
> > syslog output:
> > Mar 28 04:16:39 sxb udev[2579]: parse error
> > /etc/udev/rules.d/nut-usbups.rules, line 4:0, rule skipped
> > Mar 28 04:16:39 sxb udev[2579]: parse error
> > /etc/udev/rules.d/nut-usbups.rules, line 5:0, rule skipped
> > and :
> > # MGE UPS SYSTEMS - usbhid-ups
> > SYSFS{idVendor}="0463", SYSFS{idProduct}="ffff", MODE="664", GROUP="nut"
> > SYSFS{idVendor}="0463", SYSFS{idProduct}="0001", MODE="664", GROUP="nut"
> > --> No more errors in the syslog
>
>This is not what we want. The '=' sign, means an assignment is made,
>while we really want to do a comparison '=='.
>
>I'm not 100% sure, but I suspect this might be a RedHat bug. The scripts
>work as expected here, although I don't have a UPS handy to test this
>with (someone on this list promised one, but so far it has not arrived).
>
>Best regards, Arjen