What exactly does USR1 signal do?

Enrico Ng · 17th June 2003, 22:25

Well, I pretty much finished writing my perl scrits.
I basically made a playlist but everyother line has a comment with a ID#, the song path, a flag to show if it has been requested, and other statistics I might record.
I have shuffle turned off.
My perl script runs every 3 hours (the play list is 3 hours long) and shuffles the playlist and sends the USR1 signal.

I have a webpage that lists the songs on the playlist and shows which one is currently playing. There is a skip button to send the skip signal and a request button on each song. This finds the current song (from the log file) and locates the position on the play list, and moves that and everything above it to the bottom of the list. It keeps the songs with the "request" flag set at the top. Then the requested song is moved to the top (just below previously requested songs) and the USR1 signal is sent.

Every time the web UI script or the update script is run, it clears the request flag.

All this seems to work ok except I havent had the guts to try putting in lots of request to see what happens.
I only have one slight bug I've noticed. If the USR1 signal is sent to update the play list after a song has been "DECODE"ed but before the "TITLE" has been updated, the title will be invalid and full of garbage.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode

17th June 2003, 22:25	#20
Enrico Ng Junior Member Join Date: Jun 2003 Posts: 24	Well, I pretty much finished writing my perl scrits. I basically made a playlist but everyother line has a comment with a ID#, the song path, a flag to show if it has been requested, and other statistics I might record. I have shuffle turned off. My perl script runs every 3 hours (the play list is 3 hours long) and shuffles the playlist and sends the USR1 signal. I have a webpage that lists the songs on the playlist and shows which one is currently playing. There is a skip button to send the skip signal and a request button on each song. This finds the current song (from the log file) and locates the position on the play list, and moves that and everything above it to the bottom of the list. It keeps the songs with the "request" flag set at the top. Then the requested song is moved to the top (just below previously requested songs) and the USR1 signal is sent. Every time the web UI script or the update script is run, it clears the request flag. All this seems to work ok except I havent had the guts to try putting in lots of request to see what happens. I only have one slight bug I've noticed. If the USR1 signal is sent to update the play list after a song has been "DECODE"ed but before the "TITLE" has been updated, the title will be invalid and full of garbage.