The owner and group of mplayer.sh is already slimserver and the
permissions as you said. These are OK if the they remain the same and
if the slimserver is being run as a daemon by the slimserver userid.
What can happen is that the user installing AlienBBC is not slimserver
or root - the owner / g
I keep solving this problem from scratch every time I upgrade SlimServer
or get new hardware... slow learner, I guess. But today I actually paid
a bit of attention to what I did.
In my case it wasn't the location of the file, but the permissions on
Bin/mplayer.sh Fresh out of the AlienBBC archiv
It looks like /usr/share/slimserver/Bin will do. Here is the output:
2006-09-23 15:32:04.8392 Checking for mplayer.sh in
/usr/sbin/Bin/i386-linux/mplayer.sh
2006-09-23 15:32:04.8406 Checking for mplayer.sh in
/usr/sbin/Bin/linux/mplayer.sh
2006-09-23 15:32:04.8418 Checking for mplayer.sh in
/usr/
I don't know where mplayer.sh should be in Debian but it probably
should be in the same directory as binaries such as flac, sox and
mov123.
You could also try d_path to find where slimserver is looking for these
files.
--
bpa
---
