Can udev manage /sys/class/leds

[christophe leroy]

Hi,

I've never used udev, and would like to know if it could be the solutio=
n=20
for changing permission on /sys/class/leds/ attributes.

I can change permissions and ownership at startup for existing files bu=
t=20
new attributes created during runtime (for instance delay_on and=20
delay_off when changing the trigger to blinking) are created with root=20
permission only.
I need /sys/class/leds/ attributes owned and permitted to users of grou=
p=20
'led'.

Can udev manage that ?

Christophe

---
Ce courrier =E9lectronique ne contient aucun virus ou logiciel malveill=
ant parce que la protection avast! Antivirus est active.
http://www.avast.com

--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug=
" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Greg KH]

Hi,
I've never used udev, and would like to know if it could be the solution
for changing permission on /sys/class/leds/ attributes.

Why would the permissions need to be changed? What would you change
them to, and what would that be based on?

I can change permissions and ownership at startup for existing files but
new attributes created during runtime (for instance delay_on and
delay_off when changing the trigger to blinking) are created with root
permission only.
I need /sys/class/leds/ attributes owned and permitted to users of group
'led'.
Can udev manage that ?

Yes it can tell other programs to do that, look at how the console owner
is handled by the system to give proper ownership of audio and other
device nodes when it is determined it is valid to do so.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html