[icecast-dev] ices: forcing an immediate reread of the playlist

Michael Smith msmith at labyrinth.net.au
Tue Mar 19 15:24:51 PST 2002

At 12:32 PM 3/19/02 -0500, you wrote:
>Hi all,
>	I'm currently trying to set up ices2 with icecast2 along with otto, a 
>jukebox interface written in perl. Otto allows the user to kill a song via 
>the web interface, which in turn kills all running instances of ices, 
>rewrites the playlist and launches ices. This has the bad side effect of 
>terminating the client's connection to icecast and leaving a bunch of ices 
>dangling . I'd like to be able to have otto spawn a single instance of ices 
>at startup, and then signal ices when the user has selected the next song.
>	As far as I can tell im_playlist doesn't check for pl->nexttrack until it 
>is at the end of the file. What would be the best way to force this tight 
>loop to immediately reread it's playlist? I see two options

It'll skip to the next file if you send ices SIGHUP (I think. I may have
ended up using a different signal). It definately doesn't wait until
end of file to check that.


<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.

More information about the Icecast-dev mailing list