Timeline for systemd user service shows status "dead" on boot, but runs when manually restarted
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2023 at 22:26 | comment | added | user10489 | There are two ways to handle this I think... You can set up the user to auto log in, or you can also start the sound services in your service. | |
| Feb 12, 2023 at 16:46 | comment | added | meeotch | Thanks for the reply. And yeah, I got my list of user targets from the thread linked above, via ls /usr/lib/systemd/user/*.target - there's not a whole lot to choose from. But as mentioned, I eventually want to turn off the desktop GUI, and let this thing run headless & unattended. As a user startup script, I've got to roll my own logic for catching its exit codes, restarting it when appropriate, etc. - all the things that services are supposed to be for. I'd initially installed it as a system service, which felt more appropriate, it's the userland thing with pulse that prevented that. | |
| Feb 12, 2023 at 13:50 | history | answered | user10489 | CC BY-SA 4.0 |