There is most likely a bug affecting all Shibby and Toastman builds for the Asus RT-N66U.
I have experienced this issue on all the Toastman and Shibby builds that I have tried.
When executing scripts, for instance Optware startup scripts they only execute as they suppose to do in about 50% of all tries.
I have been in contact with a few other RT-N66U owners having the very same issues.
Here is a example script containing the "case directive" pointing out what happens:
#!/bin/sh
case "$1" in
test)
echo "test working"
;;
*)
echo "Usage: `basename $0` {case parameter failed}"
;;
esac
Running this script manually a few times in a row gives me the following result.
Tomato v1.28.0497 MIPSR2-Toastman-VLAN-RT-N K26 USB VPN-NOCAT
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
Usage: test {case parameter failed}
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
Usage: test {case parameter failed}
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
Usage: test {case parameter failed}
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
Usage: test {case parameter failed}
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
Usage: test {case parameter failed}
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /opt/etc/init.d/test test
Usage: test {case parameter failed}
I have noted tho that if I run the script the following way it works as it should.
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root# /bin/sh /opt/etc/init.d/test test
test working
root@RT-N66U:/tmp/home/root#
Not all scripts suffer from this but for instance scripts that calls the case directive do.
Please look in to this issue, as it is now Tomato is totally useless on the Asus RT-N66U.
I can provide sysinfo if needed.