Closed jgabriel98 closed 2 years ago
This question or issue can probably be easily answered or resolved by reading the docs/wiki.
The OS referenced is unsupported.
This issue has been marked wontfix and may not be a bug at all.
/tmp
is a sewer. You should not use the common system /tmp
for IPC. Many systems will not even allow services access to /tmp
.
Raspotify has no access to /tmp
by design.
You should put fifo
's under /var/run
as per the wiki.
See a relevant issue in the snapcast repo.
Also, in the sames logs, i've found out that some lines in the .service file are not reconized by the system (running latest raspbian):
Buster is not the latest version.
Oh, didn't know that the wiki was updated with this info about fifo under /var/run
(it's been a long time that i've read through this repo docs).
But thank you so much, will test this as soon as possible.
after commit a844a33 the backend
pipe
doesn't work anymore.How to reproduce:
add the following lines to
/etc/default/raspotify
:create a pipe with read and write permissions:
mkfifo /tmp/fifo_raspotify --mode=0666
result:restart
raspotify.service
connect to device and try to start a song, it will break
note:
When reverting commit a844a33 and reproducing the steps above (also running
systemctl daemon-reload
before step 3), everything works fine.Early investigations:
The the
raspotify.service
logs (journalctl -u raspotify.service -f
) indicates problems with the pipe file visibility:Also, in the sames logs, i've found out that some lines in the
it apear only when the service is loaded, so running `systemctl daemon-reload` should make it appear.service
file are not reconized by the system (running latest raspbian):system info:
Running raspotify with no authentication