startup scripts?
Hi, is there any way to run a script on startup? I've attempted creating a service to execute my script but it doesn't run.
The script just changes the enabled/disabled wakeup value for a few usb devices in /sys/bus/usb/devices/*/power/wakeup, so that when I put my PC to sleep, only my controllers or the power button can wake the PC and there are no accidental wake ups if my mouse moves etc.
Running the script manually works, and continues to work indefinitely regardless of the number of sleep/wake cycles, however when shutting down completely or restarting, if I was booting into windows for example, I need to manually run the script again before my intended functionality resumes.
Any help would be much appreciated, thanks.
Solution:Jump to solution
I managed to get it working this morning to my surprise lol.
I created a service in /etc/systemd/system, removed all the sudo commands from my script and added a 3 second sleep timer. That didn't work and threw an error that access was denied to the script directory. I changed the location of my script from /home/kyle/scripts/startup/ to /usr/local/bin/ and that worked once I updated the service file to match.
Thanks for all your help in figuring it out!!...
34 Replies
kde has a autostart category in settings
gnome should have it in gnome tweaks
No luck with this, whenever I restart, the autostart tab in settings just says "Not yet autostarted" next to my script. I have attempted to run it as a program which created a .desktop file in the autostart directory, but this also didn't work. I recreated the original script within the autostart directory too.
For clarification I'm using KDE not Gnome.
make sure you're actually executing the script with bash
How do I make sure the script is executing with bash using the autostart function?
execute it with /bin/bash
@Clint Bollywood
Is that within the script itself? Or the autostart settings?
I'm very new to Linux apologies if that's a simple question
When I created the script I added #!/bin/bash to the first line if that's what you mean?
in the .desktop file
you can select a program
make sure the first line for the script is
#!/usr/bin/bash and its executable
/bin/bash is the same as /usr/bin/bash here tooThe first line of the script is #!/bin/bash/ and I haveade it executable with chmod +x followed by the path to the script.
I currently have the script added to steam and when I run it from there it works and sets the right wakeup values so the script is working
remove the
/ at the endDidn't mean to type the / at the end on my message, the / isn't there on the script
and if you need to make a systemd service
if it needs root access then put it in
/etc/systemd/system/blah.unit (do not use sudo in the script)
if it runs as user then you can put it in
/etc/systemd/user/blah.unit or ~/.config/systemd/user/blah.unit
this is a simple "run the script" service unit you can modify
forgot if its default or multi-user that works in gamemode, cant check as im heading out the door
the you do systemctl daemon-reload and enable the sevice
note: if its a user service use systemctl with the --user flagI'll try this when I next get chance, thank you!!
When I previously tried the systemd method, I used a .service file and used systemctl enable --now file path
Is a .unit file different?
I was actually looking at running a script as well but my command requires root and sudo, what's the reason we shouldn't have sudo in the script?
because the units in
system run as root
so you dont need sudoI do apologize, I'm also new to this, but if I'm understanding correctly I can just remove sudo from the command and keep the rest as is?
yep
as long as the script is run by a system service you dont need sudo in the script 🙂
I've attempted this with both multi-user and default, running from /etc/systemd/system/usb-wake-fix.unit but neither have worked when booting up.
Is there no other way to set the USB wakeup state per device?
I'm at a loss for why the script doesnt run
show me the script
I also removed sudo from each command in the script and added a 10 second sleep command just in case it was being overwritten
I'll send it as soon as I get back to my pc
well im about to head off so might not respond until tomorrow
#!/bin/bash
sleep 10
chmod 666 /sys/bus/usb/devices/1-7.2/power/wakeup
echo "disabled" > /sys/bus/usb/devices/1-7.2/power/wakeup #disables keyboard usb wakeup
chmod 644 /sys/bus/usb/devices/1-7.2/power/wakeup
chmod 666 /sys/bus/usb/devices/1-13.4/power/wakeup
echo "disabled" > /sys/bus/usb/devices/1-13.4/power/wakeup #disables mouse usb wakeup
chmod 644 /sys/bus/usb/devices/1-13.4/power/wakeup
chmod 666 /sys/bus/usb/devices/1-13.1/power/wakeup
echo "enabled" > /sys/bus/usb/devices/1-13.1/power/wakeup #enables bluetooth usb wakeup
chmod 644 /sys/bus/usb/devices/1-13.1/power/wakeup
and what does
systemctl status usb-wake-fix showUsb-wake-fix could not be found
It's a .unit file, should I make it a .service file instead?
yes it should be .service, sorry im used to calling them unit files as thats what they have been referred to in the past 😅
No worries, I'll try again tomorrow and report back, hopefully that will fix it 🤣
Thanks for all the help so far
the script should work from the look of it and its late enough in the boot for it to have everything populated
Awesome! I'll give it a shot!
Solution
I managed to get it working this morning to my surprise lol.
I created a service in /etc/systemd/system, removed all the sudo commands from my script and added a 3 second sleep timer. That didn't work and threw an error that access was denied to the script directory. I changed the location of my script from /home/kyle/scripts/startup/ to /usr/local/bin/ and that worked once I updated the service file to match.
Thanks for all your help in figuring it out!!
yeah script files have to be in a system location (unless its a user service)
That makes a lot of sense I'm not sure why I didn't think of it earlier. Oh well, I've learned something new today. As confusing as this linux journey is, I'm loving the challenge 🤣
a lot of things in the end is sensible when you look at it
until you run into a command that has something like
pin --unpin as arguments 🤣I'm hoping at least for now that I don't have to go much deeper than this 🤣