* Joe Beiter schrieb am 27.09.04 um 20:47 Uhr:
>
> I'm running web services on an alternate unused port.
> I noticed when trying to play a song, xmms or
> realplayer is trying to connect to my host on port 80.
>
> ie: I connect to http://hostname:2430/jamdb, pick out
> a song to listen to, then my mp3 player tries to
> connect back on port 80. Is this port being defined by
> the server, or the client?
misconfigurstion?
>
> Also, when I try to point my player directly to
> http:hostname:2430/mp3/foo/bar/foo.mp3, I get the
> error "[Mon Sep 27 14:37:29 2004] [error] [client
> 169.144.24.3] File does not exist: /www/htdocs/mp3"
This seems not to be a JamDB problem...
>
> This is my array entry:
> -----------------------------------------
> $m3u_paths = array("Web" =>
> "http://glyph/mp3/",
> "NFS" =>
> "/mnt/server/home/mp3/",
> "Samba" => "m:/"
> );
> -----------------------------------------
Her you did not mention the port anywhere like http://glyph:2430/mp3/
or something...
> I get this error whether "mp3" is in my jamdb.conf
> entry or not. There is no file/directory called mp3 in
> /www/htdocs.. should there be a link to my music
> directory in there? I assumed jamdb would interpret
> it, based on the entries in jamdb.config.
But /www/htdocs is your webservers DocRoot, right?
>
> cutpath entry is: define("CUT_PATH", "/home/jwb/");
>
> My mp3 directory is in there.
ok, but you must be able to browse to your songs with xour browser,
because your player will try the same...
Maybe 0.9.9 will have an option to stream songs without having the
requirement of having direct access to them.
>
>
> Thirdly... is 0.9.9 available anywhere? The one with
> the reworked configuration? ;-)
Its not released yet.
-Marc
--
8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134
|
