Without this, /etc/init.d/led will try to set the non-existing 'rssi' trigger.
This doesn't harm as the kernel will refuse this setting, but it outputs some
ugly log-lines:
Jun 24 10:15:19 OpenWrt user.info sysinit: setting up led RSSILOW
Jun 24 10:15:19 OpenWrt user.info sysinit: sh: write error: Invalid argument
...

In order to avoid this, skip LEDs with trigger = "rssi" in /etc/init.d/led

Signed-off-by: Daniel Golle <dgo...@allnet.de>

diff --git a/package/base-files/files/etc/init.d/led 
b/package/base-files/files/etc/init.d/led
index 43964bf..f3f3c3f 100755
--- a/package/base-files/files/etc/init.d/led
+++ b/package/base-files/files/etc/init.d/led
@@ -25,6 +25,11 @@ load_led() {
        config_get interval $1 interval "50"
        config_get port_state $1 port_state
 
+       if [ "$trigger" = "rssi" ]; then
+               # handled by rssileds userspace process
+               return
+       fi
+
        [ -e /sys/class/leds/${sysfs}/brightness ] && {
                echo "setting up led ${name}"
                [ "$default" != nil ] && {
-- 
1.7.12

Attachment: pgpDLodZb1T3s.pgp
Description: PGP signature

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to