this post was submitted on 09 Apr 2024
314 points (98.8% liked)

Linux

48310 readers
645 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

I thought I'll make this thread for all of you out there who have questions but are afraid to ask them. This is your chance!

I'll try my best to answer any questions here, but I hope others in the community will contribute too!

you are viewing a single comment's thread
view the rest of the comments
[–] baseless_discourse@mander.xyz 9 points 7 months ago* (last edited 7 months ago) (4 children)

If you run a systemd distro (which is most distro, arch, debian, fedora, and most of their derivatives), you can create a service file, which will autostart as root on startup.

The service file /etc/systemd/system/<your service>.service should like

[Unit]
Description=some description

[Service]
ExecStart=alsactrl restore

[Install]
WantedBy=multi-user.target

then

systemctl enable <your service>.service --now

you can check its status via

systemctl status <your service>.service

you will need to change <your service> to your desired service name.

For details, read: https://linuxhandbook.com/create-systemd-services/

[–] HATEFISH@midwest.social 2 points 7 months ago (3 children)

This one seemed perfect but nothing lasts after the reboot for whatever reason. If i manually re-enable the service its all good so I suspect theres no issue with the below - I added the after=multi-user.target after the first time it didn't hold after reboot.


[Unit]
Description=Runs alsactl restore to fix microphone loop into headphones
After=multi-user.target
[Service]
ExecStart=alsactl restore

[Install]
WantedBy=multi-user.target

When I run a status check it shows it deactivates as soon as it runs

Apr 11 20:32:24 XXXXX systemd[1]: Started Runs alsactl restore to fix microphone loop into headphones.
Apr 11 20:32:24 XXXXX systemd[1]: alsactl-restore.service: Deactivated successfully.
[–] baseless_discourse@mander.xyz 2 points 7 months ago* (last edited 7 months ago) (2 children)

Does after=... solve the problem or cause the problem? Sorry, I cannot parse what you were trying to say.

[–] HATEFISH@midwest.social 2 points 7 months ago (1 children)

It seems to have no effect either way. Originally I attempted without, then when it didn't hold after a reboot and some further reading I added the After= line in attempt to ensure the service isn't trying to initiate before it should be possible.

I can manually enable the service with or without the After= line with the same results of it actually working. Just doesn't hold after a reboot.

[–] baseless_discourse@mander.xyz 2 points 7 months ago* (last edited 7 months ago)

That is interesting. BTW, I don't assume that command will run forever right, i.e. it will terminate relatively soon? so that could be why the service is deactivated, not because it is not run. You can try to add ; echo "command terminated" at the end of ExecStart to see if it is terminated, you can also try to echo the exit code to debug.

If the program you use has a verbose mode, you can also try to turn it on to see if there is any error. EDIT: indeed, alsactrl restore --debug

There is also a possiblity that this service is run before the device you need to restore is loaded, so it won't have any effect.

On a related note, did you install the program via your package manager, and what distro are you running. Because sometimes SELinux will block the program running. But the error message will say permission denied, instead of your message.