Open nonbinary opened 8 years ago
Hi @nonbinary thank you for looking at this, I haven't tested or run it for years now so I can't give you the status on this configuration.
Do you think you could add a pull-request with your daemon.conf
and a note in the README for debian ? Saying "needed for me" maybe needed for you. It will be better than an issue to document this.
I'm afraid I've made quite a few changes to that daemon.conf file, and I can't really say that I've got it at hand anymore. But I do no that at the time it was a clean install, with just the pid-file line in daemon.conf. I was thinking that since your setup here used command-line flags instead of changing daemon.conf, it'd be more consistent to add it to the service file.
I followed this on a Raspberry Pi running Debian, and it worked quite fine. I did have one hiccup though - pulseaudio got a SIGTERM right after systemd finished starting up the service. I got away from this by adding
--use-pid-file
to the command line, and then specifyingPIDFile=/var/run/pulse/pid
in the systemd service file. Or, well, to be exact I didn't use flags in the ExecStart command line, I specified it all in/etc/pulse/daemon.conf
.Now, I'm not sure if this is needed to get it running nowadays on Arch, but it's the only step that was missing on debian.