[GH-ISSUE #258] daemon log to STDOUT and no double fork #1068

New issue

Open

opened 2026-03-14 13:18:21 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 13:18:21 +03:00

Owner

Originally created by @chrisaq on GitHub (Sep 26, 2023).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/258

Is your feature request related to a problem? Please describe.
The common way to run linux daemons lately have been to not (double) fork the process, but let it run in the foreground.
This lets you see the logs using docker logs, journalctl -u <service> , kubectl logs and so on.

Describe the solution you'd like
Give spotify_player daemon and extra option to not daemonize, and print logs to STDOUT.

Describe alternatives you've considered
There are really no alternatives if you want to achieve this and use standard tools for reading logs the normal way.
For systemd there are workarounds for forking daemons, but it is not recommended.

Additional context
I've not been able to find how to do this with spotify-player as is, please excuse me if that is the case after all.

Originally created by @chrisaq on GitHub (Sep 26, 2023). Original GitHub issue: https://github.com/aome510/spotify-player/issues/258 **Is your feature request related to a problem? Please describe.** The common way to run linux daemons lately have been to not (double) fork the process, but let it run in the foreground. This lets you see the logs using `docker logs`, `journalctl -u <service>` , `kubectl logs` and so on. **Describe the solution you'd like** Give `spotify_player daemon` and extra option to not daemonize, and print logs to STDOUT. **Describe alternatives you've considered** There are really no alternatives if you want to achieve this and use standard tools for reading logs the normal way. For systemd there are workarounds for forking daemons, but it is not recommended. **Additional context** I've not been able to find how to do this with spotify-player as is, please excuse me if that is the case after all.