| View previous topic :: View next topic |
| Author |
Message |
Anonymous
Guest
|
 Posted: Sat Feb 11, 2006 3:47 pm Post subject: Signal to re-read icecast.xml |
 |
|
Is there a signal that I can send to icecast2 that will force it to re-read icecast.xml? The fallback mount on one of my mounts is a static mp3 file, which is actually a soft-link to another mp3 that I change on the fly. However, once icecast reads the original mp3 file, it never goes back and re-loads the mp3 which may now be soft-linked to another file.
So I thought that if there were a way to signal icecast to re-read the .xml, I could get it to pick up a new mp3 that the fallback mount is linked to. |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Sat Feb 11, 2006 6:21 pm Post subject: |
|
|
SIGHUP should allow for changes to fallback, applies to intro filename changes as well.
karl. |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Sat Feb 11, 2006 11:45 pm Post subject: |
|
|
Hmm .. doesn't seem to have the desired effect.
I have:
<fallback-mount>/Track30.mp3</fallback-mount>
<fallback-override>1</fallback-override>
where Track30.mp3 is symlinked to voice1.mp3
I broke the symlink to voice1.mp3 and created a new link to voice2.mp3
I then issued a kill -SIGHUP <pid> (to each of the icecast instances)
During the next fallback cycle, voice1.mp3 still was streamed. I guess it has a memory like an elephant! |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
