I made a script that controls my system LEDs and it works great. I saved it to /usr/local/bin/led-pattern and ran sudo chmod a+x /usr/local/bin/led-pattern so its executable simply by entering the command led-pattern. Upon doing so, it asks for an administrative password, and upon entering the password, the script runs as intended. However, when added to my list of startup applications, it does not run at login, presumably because of the lack of sudo permissions, as all my other startup scripts that I've made work just fine and don't require permission. How can I make it so that this script runs at startup seamlessly - never asking for any password even though it requires sudo permissions?
Edit: by startup, I mean while it's logging the user on, not while booting up the computer
sudocommand in the script. If you remove the sudo commands and call the script from /etc/rc.local, it should run as root at startup. When you call it from the command line, you will need to prefix the script with sudo – Nick Sillito Dec 31 '16 at 07:20sudos in the script – cheesits456 Dec 31 '16 at 07:21/etc/rc.locala default file or folder and does he have to create it ? – George Udosen Dec 31 '16 at 07:32sudos from the script, since the root user, by default, can run sudo without password – muru Dec 31 '16 at 07:34sudoabsolutely necessary in your script ? If not, remove it. Alternatively, find out to which group that command belongs withls -l /path/to/command/binary. If it's anything other thanroot, consider adding yourself to that group. Then you will be able to run without need forsudo. That's first. Second, is it absolutely necessary to run when logging-in or can it run when login screen shows up ? There are ways to run scripts as root at login screen itself. – Sergiy Kolodyazhnyy Dec 31 '16 at 09:45