So far I?m getting insults and claims that I don?t know what I?m doing and my Webmaster doesn?t know what he?s doing, even though he?s worked for large bluechip companies. Please make an effort to actually respond to what I asked, and don?t presume to tell me what I did wrong and how it?s my fault ? or his fault. I assume the distribution is the one on the Icecast site. I have a CentOS 6.5 server, using cPanel/WHM. Stop talking down to me and give me a real step-by-step answer. Gene Steinberg> On Sep 26, 2014, at 1:05 PM, Thomas B. R?cker <thomas at ruecker.fi> wrote: > > On 09/26/2014 07:15 PM, Gene Steinberg wrote: >> Linked file means the original MP3 file posted on the server. >> >> init script? Tell me where to find one? That?s what the Web guy evidently didn?t know, since he?s not experienced at Icecast. > > If Icecast was installed from a distribution package, then there usually > is a distribution specific way to start/stop/etc the server, in this > case Icecast. In most cases this is an init script. Although nowadays > systemd is becoming more popular and there it would be a service > definition file. > > Long story short: > There should be one already. Depending on what your "web guy" did to > Icecast and its configuration, it may or may not work though. > > It sounds like what you need is a proper system administrator and not a > "web guy". > > > Cheers > > Thomas > > > >>> On Sep 26, 2014, at 12:11 PM, Thomas B. R?cker <thomas at ruecker.fi> wrote: >>> >>> On 09/26/2014 01:57 PM, Gene Steinberg wrote: >>>> Well, not quite. The radio network that carries my two radio shows does on-demand and live. >>>> >>>> We just wanted an on-demand streamer for our own needs. >>> I don't understand why you call this on demand, but then use a source >>> client to stream it, that's not really on-demand, that's still >>> considered streaming. >>> >>> On demand is usually considered something where the content is always >>> started from the beginning (unless client and server explicitly >>> implement resume). >>> >>>> The code from our webmaster to update after a linked file is replaced is: >>> What is a "linked file"? What does this mean? >>> >>> >>>> 1) You need to update the playlist file with the new show. >>>> >>>> A) PARACAST FILE LIVES HERE: /usr/local/etc/paracast.m3u >>>> B) TECH NIGHT OWN FILE LIVES HERE: /usr/local/etc/nightowl.m3u >>> Given that the file names here match the file names in 3) (except the >>> m3u/cfg file extension), I'm going to guess that those are play lists >>> that then are being streamed. >>> >>> >>>> 2) Shut down/restart icecast. (there may be ways of not having to restart the stream, but it's beyond me) >>>> >>>> A) RUN THIS COMMAND: ps -C icecast >>>> B) Get the PID # that is shown for icecast >>>> C) RUN THIS COMMAND (where PID# is from above): kill PID# >>>> D) RUN THIS COMMAND: /usr/bin/icecast -c /etc/icecast.xml -b >>>> E) You MIGHT have to hit CTRL-C after that last step to return to prompt. >>> This is most certainly NOT necessary. What would make you think that you >>> need to do this? >>> Also why are you not using an init script? >>> >>> >>>> 3) Restart icegenerator (this is what serves the mp3 files to icecast) >>>> >>>> A) RUN THIS COMMAND: /usr/local/bin/icegenerator -f /usr/local/etc/paracast.cfg >>>> B) RUN THIS COMMAND: /usr/local/bin/icegenerator -f /usr/local/etc/nightowl.cfg >>>> >>>> So what am I missing? Can we make this dynamic? >>> I'm not familiar with Icegenerator. >>> Have you tried reading its documentation? >>> http://www.becrux.com/index.php?page=projects&name=icegenerator >>> >>> If that doesn't fit your bill you could switch to a different source >>> client that's capable to reload its play list dynamically. That might be >>> e.g. ez-stream, but there are many. >>> >>> >>> Cheers >>> >>> Thomas >>> >>> >>>>> On Sep 25, 2014, at 11:56 PM, Thomas B. R?cker <thomas at ruecker.fi> wrote: >>>>> >>>>> On 09/26/2014 12:39 AM, Gene Steinberg wrote: >>>>>> So I have a new Icecast setup with two channels, each of which carries a link to MP3 files. >>>>> Icecast is intended for live streaming, not for serving static files. >>>>> Which of both are you doing here? >>>>> >>>>> >>>>>> Whenever I update the .m3u file to reflect a changed link, I have to restart Icecast and the Icegenerator to make it recognize the change. >>>>> Where do you update a m3u file? Icecast generates dynamic m3u files for >>>>> streams, so creating your own is usually not necessary. >>>>> Or is this something in your source client side (Icegenerator?). >>>>> >>>>> Cheers >>>>> >>>>> Thomas >>>>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast
Gene Steinberg:> Stop talking down to me and give me a real step-by-step answer.interesting mentality. i'd suggest to read the docs: http://icecast.org/docs/ really, it helps. --u
Thanks for not being helpful. Which section of the manual do I search for, since it?s divided into several sections? Or just quote the passage. Is that too hard? Interesting mentality indeed. I do not see why one needs to take a holier-than-thou attitude in answering a simple question. Gene Steinberg> On Sep 26, 2014, at 5:31 PM, uno <un at dom.de> wrote: > > Gene Steinberg: >> Stop talking down to me and give me a real step-by-step answer. > > interesting mentality. > i'd suggest to read the docs: http://icecast.org/docs/ > really, it helps. > --u > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast
On 09/26/2014 10:33 PM, Gene Steinberg wrote:> Please make an effort to actually respond to what I asked, and don?t presume to tell me what I did wrong and how it?s my fault ? or his fault.That's exactly what I'm doing, I'm trying to figure out what situation you are in, so that I can properly respond to your questions, without having to resort to guessing and assumptions. This inevitably leads to more questions, before you start getting answers. So far the situation is becoming more clear but there are still fairly many question marks preventing me from giving you a concise and targeted answer.> I assume the distribution is the one on the Icecast site. I have a CentOS 6.5 server, using cPanel/WHM.The clean way to install Icecast on CentOS6 would be from the EPEL6 repository. RPMforge maybe too (haven't tried myself). A third option would be that a package of Icecast 2.4 from my OBS repository was installed. In addition there are: - SRPM rebuilt and installed - built and installed from source It would help us to help you further if you could clarify how Icecast was installed on the machine. You can do this by e.g. checking which repositories are enabled and by checking the package version of Icecast using the 'rpm' command. Probably something like "rpm -q icecast". In most cases you'll have an init script and can use: /etc/init.d/icecast That will give you control of the Icecast server process. Seeing that icegenerator is in /usr/local that means it was installed from source, combined with the instructions you posted previously there seems to be no init script for that. To sum up, I can currently state: - Use the init script to start/stop Icecast - Follow the instructions given to you for the rest Regarding your "dynamic reload" problem, my previous statement remains. "I'm not familiar with Icegenerator. Have you tried reading its documentation? http://www.becrux.com/index.php?page=projects&name=icegenerator If that doesn't fit your bill you could switch to a different source client that's capable to reload its play list dynamically. That might be e.g. ez-stream, but there are many." If you give us some more information about your work flow for populating those playlists someone on the list might be able to suggest a better suited source client or a modifictation to your current setup.> give me a real step-by-step answer.Without understand your situation fully, it is impossible to give you "exact steps". At the risk of angering you further I'm going to say, that what you are asking for goes in some aspects beyond the scope of this list: We offer help to people who want to figure things out and help themselves, we do not do individual project work on behalf of other people. That said you are welcome to solicit paid help for your particular setup on this list. Usually we see several answers to such requests. Best regards Thomas Ruecker> Gene Steinberg > > >> On Sep 26, 2014, at 1:05 PM, Thomas B. R?cker <thomas at ruecker.fi> wrote: >> >> On 09/26/2014 07:15 PM, Gene Steinberg wrote: >>> Linked file means the original MP3 file posted on the server. >>> >>> init script? Tell me where to find one? That?s what the Web guy evidently didn?t know, since he?s not experienced at Icecast. >> If Icecast was installed from a distribution package, then there usually >> is a distribution specific way to start/stop/etc the server, in this >> case Icecast. In most cases this is an init script. Although nowadays >> systemd is becoming more popular and there it would be a service >> definition file. >> >> Long story short: >> There should be one already. Depending on what your "web guy" did to >> Icecast and its configuration, it may or may not work though. >> >> It sounds like what you need is a proper system administrator and not a >> "web guy". >> >> >> Cheers >> >> Thomas >> >> >> >>>> On Sep 26, 2014, at 12:11 PM, Thomas B. R?cker <thomas at ruecker.fi> wrote: >>>> >>>> On 09/26/2014 01:57 PM, Gene Steinberg wrote: >>>>> Well, not quite. The radio network that carries my two radio shows does on-demand and live. >>>>> >>>>> We just wanted an on-demand streamer for our own needs. >>>> I don't understand why you call this on demand, but then use a source >>>> client to stream it, that's not really on-demand, that's still >>>> considered streaming. >>>> >>>> On demand is usually considered something where the content is always >>>> started from the beginning (unless client and server explicitly >>>> implement resume). >>>> >>>>> The code from our webmaster to update after a linked file is replaced is: >>>> What is a "linked file"? What does this mean? >>>> >>>> >>>>> 1) You need to update the playlist file with the new show. >>>>> >>>>> A) PARACAST FILE LIVES HERE: /usr/local/etc/paracast.m3u >>>>> B) TECH NIGHT OWN FILE LIVES HERE: /usr/local/etc/nightowl.m3u >>>> Given that the file names here match the file names in 3) (except the >>>> m3u/cfg file extension), I'm going to guess that those are play lists >>>> that then are being streamed. >>>> >>>> >>>>> 2) Shut down/restart icecast. (there may be ways of not having to restart the stream, but it's beyond me) >>>>> >>>>> A) RUN THIS COMMAND: ps -C icecast >>>>> B) Get the PID # that is shown for icecast >>>>> C) RUN THIS COMMAND (where PID# is from above): kill PID# >>>>> D) RUN THIS COMMAND: /usr/bin/icecast -c /etc/icecast.xml -b >>>>> E) You MIGHT have to hit CTRL-C after that last step to return to prompt. >>>> This is most certainly NOT necessary. What would make you think that you >>>> need to do this? >>>> Also why are you not using an init script? >>>> >>>> >>>>> 3) Restart icegenerator (this is what serves the mp3 files to icecast) >>>>> >>>>> A) RUN THIS COMMAND: /usr/local/bin/icegenerator -f /usr/local/etc/paracast.cfg >>>>> B) RUN THIS COMMAND: /usr/local/bin/icegenerator -f /usr/local/etc/nightowl.cfg >>>>> >>>>> So what am I missing? Can we make this dynamic? >>>> I'm not familiar with Icegenerator. >>>> Have you tried reading its documentation? >>>> http://www.becrux.com/index.php?page=projects&name=icegenerator >>>> >>>> If that doesn't fit your bill you could switch to a different source >>>> client that's capable to reload its play list dynamically. That might be >>>> e.g. ez-stream, but there are many. >>>> >>>> >>>> Cheers >>>> >>>> Thomas >>>> >>>> >>>>>> On Sep 25, 2014, at 11:56 PM, Thomas B. R?cker <thomas at ruecker.fi> wrote: >>>>>> >>>>>> On 09/26/2014 12:39 AM, Gene Steinberg wrote: >>>>>>> So I have a new Icecast setup with two channels, each of which carries a link to MP3 files. >>>>>> Icecast is intended for live streaming, not for serving static files. >>>>>> Which of both are you doing here? >>>>>> >>>>>> >>>>>>> Whenever I update the .m3u file to reflect a changed link, I have to restart Icecast and the Icegenerator to make it recognize the change. >>>>>> Where do you update a m3u file? Icecast generates dynamic m3u files for >>>>>> streams, so creating your own is usually not necessary. >>>>>> Or is this something in your source client side (Icegenerator?). >>>>>> >>>>>> Cheers >>>>>> >>>>>> Thomas >>>>>> >>>>>>
epicanis+icecast at dogphilosophy.net
2014-Sep-27 15:49 UTC
[Icecast] Automatic Update of MP3 Files
Okay, I'm pretty new to icecast myself, and have had to work my way through the same kind of confusion, so I think I know where you're coming from here. Part of the problem is that what you're describing and asking for doesn't really make sense...except that I know I'd have been mis-describing my situation pretty much the same way not too long ago so I think I understand what you mean (and I can make a couple of suggestions). I would suggest that icecast actually has nothing to do with your situation (read below) - you can therefore probably ignore all the stuff about init scripts[1] for icecast in the previous discussion if you want. Read on for some possible solutions...> >>>>>> On 09/26/2014 12:39 AM, Gene Steinberg wrote: >So I have a new Icecast setup with two channels, each of which carries a link >to MP3 files.So, you have an icecast server configured to handle two independent streams of mp3 data, each of which is coming from a running copy of "icegenerator"? Part of the confusion up to this point is that icecast doesn't read mp3 files, or m3u files, or anything else except its own configuration file, but I think Mr. Ruecker is assuming that since you are being told to restart icecast by hand anyway that there's something very odd in icecast's setup, and if he gives you a typical way of dealing with this situation it will at best just not work, and at worst break something. He's not being insulting - the description you've given is a bit confusing. I imagine it is worse for someone whose first language may not be English. (I also have to admit that what you've described doesn't sound like the way most system administrators would usually choose to install and configure things, suggesting that they're either relatively new to it, OR are dealing with some kind of unusual situation that might make typical approaches to fixing things difficult or counterproductive.) icecast is a much simpler, "dumber" program than it looked like to me when I first heard about it and started trying to use it. Icecast only takes a "live" stream of audio or video data and passes copies of that "live" stream to media players that have connected to it, and nothing more. It has no idea if the "live stream" is coming from an actual live recording, or one giant .mp3 file, or a series of .mp3 files listed in a .m3u file and streamed to it one after the other, or what. All of those details are handled by the "source client", which in your case is icegenerator.>Whenever I update the .m3u file to reflect a changed link, I have to restart >Icecast and the Icegenerator to make it recognize the change.I *suspect* that you actually *don't* have to restart icecast, and the person who told you that it was necessary is mistaken (again, not too long ago I'd have also assumed that icecast needed to be restarted, too, but now that I've had a little time to experiment that doesn't seem to be the case). The only thing I can figure is you've been told to do that because the icegenerator processes will die when the icecast connection they're talking to goes down. ("killall icegenerator" seems like it'd be simpler, though). On my own setup, when the "source client" ("oggfwd" sending a stream of .opus data in my case, but this doesn't really matter) disconnects, the "channel" on my icecast server disappears. When it reconnects, the channel reappears and people can connect to it again. I find I don't need to restart icecast for this.>Is there a way to automate this process? So when I update the file link, >that?s reflected in the stream, which auto updates too?Yes...probably. I think the problem is entirely just that icegenerator only looks at the .m3u file when it first starts up, and then after it has loaded the playlist into memory it closes the file and forgets about it. That would explain why you have to restart icegenerator every time you change the file. How easy it would be to automate handling this kind of depends on how picky you are about exactly what you're asking.>How do I go about this?My initial suggestion would be to try a different source client. I know ices2 apparently watches the playlist file (if that's where it's source material is coming from) for changes and automatically handles this, though it is only for .ogg [vorbis] files (I really wish it was updated to support .opus as well...). There is an older "ices0"[2] that is written for .mp3 files. I'm not sure, but I *think* it otherwise works the same way as ices2, so it might do exactly what you want (automatically notice changes to the .m3u file and update the stream accordingly) if you replace icegenerator with it. (If it turns out that monitoring the playlist file for changes is a newer feature only implemented in ices2, there may be other source clients for the mp3 format that do what you want instead.) If you aren't willing to switch away from icegenerator for some reason, it's still possible but it's going to be more complicated. Here's what I would try: First - contact the icegenerator developers and ask about having icegenerator monitor the .m3u file for changes. It's possible that they'd be interested in adding that feature, or maybe even already have and it's just not documented. Next, as an experiment, next time you modify the .m3u file try using "killall -HUP icegenerator" (skipping the entire complex process of manually killing and restarting icecast by hand and then [re-]starting icegenerator by hand twice). The "hangup" (-HUP) signal traditionally tells daemon processes to reload their configuration files, so it's possible that command by itself will do everything that you're currently doing. There's no guarantee that icegenerator works that way, but if it does that will make things simpler. That still leaves you manually running one command after updating the .m3u files, but it's a start. If it doesn't work this way for icegenerator, that command should instead tell the instances of icegenerator to terminate normally and you can (if nothing else) manually run those last two "icegenerator" commands in your procedure as usual but skip the restarting of the icecast server. The only way to fully automate this is to have ANOTHER, separate program running to monitor the .m3u files and issue the commands for you. This is probably not an optimal way of doing it. However: There is a set of utilities called "inotifytools" that is specifically designed for watching files and directories for changes. If that is installed, supposedly, something like: while inotifywait -e modify /usr/local/etc/paracast.cfg; do killall -HUP icegenerator done run as a shell script in the background would do what you're describing for the "paracast" feed (assuming in this case that "killall -HUP icegenerator" is all you need - if you need to run other commands as well you'll have to add them...). I should also disclaim that I've never used the inotify tools before, so I can't guarantee that what I wrote there would do what I think it does. If you move the icegenerator stream config files to their own directory (e.g. /usr/local/etc/audiostreams or something of the sort) you can have inotify watch the whole directory of files at once instead of one file at a time. Yes, that was kind of long, but hopefully the situation makes a little more sense to people reading this thread (unless I've gotten confused, too.) [1] - on CentOS, I *think* (it's been a few years) that the init scripts are in /etc/init.d somewhere. The same scripts that get run automatically when the system boots up to make sure all the server programs (potentially including icecast) start up are normally ALSO used to stop or restart them. Typically if you're restarting an icecast server on CentOS, the command would be something like "/etc/init.d/icecast restart", without needing a complex series of commands typed in by hand. If those commands really ARE necessary, then there is something unusual about the way it's installed. If icecast has been installed "by hand" instead of using a CentOS ".rpm" package[3], that init file may not exist. As I mentioned, though, this probably doesn't actually have anything to do with your problem... [2] - http://icecast.org/ices/ [3] Icecast seems to be available pre-built for CentOS 6.5 in the "EPEL" repositories, so if installed from there I would expect the init scripts to be there. ices0 and icegenerator BOTH appear to be bin the "ATrpms" repository as prebuilt packages as well, so they could be installed from there instead of built and maintained manually from source. If you have the server's system administrator add those two repositories (EPEL and ATrpms), you might find it a lot easier to install and maintain than installing them by hand from source will be.
That?s better. This is helpful and I sent the information off to the Webmaster to review. Peace, Gene> On Sep 27, 2014, at 1:05 AM, Thomas B. R?cker <thomas at ruecker.fi> wrote: > > On 09/26/2014 10:33 PM, Gene Steinberg wrote: >> Please make an effort to actually respond to what I asked, and don?t presume to tell me what I did wrong and how it?s my fault ? or his fault. > > That's exactly what I'm doing, I'm trying to figure out what situation > you are in, so that I can properly respond to your questions, without > having to resort to guessing and assumptions. This inevitably leads to > more questions, before you start getting answers. > So far the situation is becoming more clear but there are still fairly > many question marks preventing me from giving you a concise and targeted > answer. > > >> I assume the distribution is the one on the Icecast site. I have a CentOS 6.5 server, using cPanel/WHM. > > The clean way to install Icecast on CentOS6 would be from the EPEL6 > repository. RPMforge maybe too (haven't tried myself). > A third option would be that a package of Icecast 2.4 from my OBS > repository was installed. > In addition there are: > - SRPM rebuilt and installed > - built and installed from source > > It would help us to help you further if you could clarify how Icecast > was installed on the machine. You can do this by e.g. checking which > repositories are enabled and by checking the package version of Icecast > using the 'rpm' command. Probably something like "rpm -q icecast". > > In most cases you'll have an init script and can use: > /etc/init.d/icecast > That will give you control of the Icecast server process. > > Seeing that icegenerator is in /usr/local that means it was installed > from source, combined with the instructions you posted previously there > seems to be no init script for that. > > To sum up, I can currently state: > - Use the init script to start/stop Icecast > - Follow the instructions given to you for the rest > > Regarding your "dynamic reload" problem, my previous statement remains. > > "I'm not familiar with Icegenerator. > Have you tried reading its documentation? > http://www.becrux.com/index.php?page=projects&name=icegenerator > > If that doesn't fit your bill you could switch to a different source > client that's capable to reload its play list dynamically. That might be > e.g. ez-stream, but there are many." > > If you give us some more information about your work flow for populating those playlists someone on the list might be able to suggest a better suited source client or a modifictation to your current setup. > > > >> give me a real step-by-step answer. > > Without understand your situation fully, it is impossible to give you > "exact steps". > At the risk of angering you further I'm going to say, that what you are > asking for goes in some aspects beyond the scope of this list: > We offer help to people who want to figure things out and help > themselves, we do not do individual project work on behalf of other people. > That said you are welcome to solicit paid help for your particular setup > on this list. Usually we see several answers to such requests. > > > Best regards > > Thomas Ruecker > >> Gene Steinberg >> >> >>> On Sep 26, 2014, at 1:05 PM, Thomas B. R?cker <thomas at ruecker.fi> wrote: >>> >>> On 09/26/2014 07:15 PM, Gene Steinberg wrote: >>>> Linked file means the original MP3 file posted on the server. >>>> >>>> init script? Tell me where to find one? That?s what the Web guy evidently didn?t know, since he?s not experienced at Icecast. >>> If Icecast was installed from a distribution package, then there usually >>> is a distribution specific way to start/stop/etc the server, in this >>> case Icecast. In most cases this is an init script. Although nowadays >>> systemd is becoming more popular and there it would be a service >>> definition file. >>> >>> Long story short: >>> There should be one already. Depending on what your "web guy" did to >>> Icecast and its configuration, it may or may not work though. >>> >>> It sounds like what you need is a proper system administrator and not a >>> "web guy". >>> >>> >>> Cheers >>> >>> Thomas >>> >>> >>> >>>>> On Sep 26, 2014, at 12:11 PM, Thomas B. R?cker <thomas at ruecker.fi> wrote: >>>>> >>>>> On 09/26/2014 01:57 PM, Gene Steinberg wrote: >>>>>> Well, not quite. The radio network that carries my two radio shows does on-demand and live. >>>>>> >>>>>> We just wanted an on-demand streamer for our own needs. >>>>> I don't understand why you call this on demand, but then use a source >>>>> client to stream it, that's not really on-demand, that's still >>>>> considered streaming. >>>>> >>>>> On demand is usually considered something where the content is always >>>>> started from the beginning (unless client and server explicitly >>>>> implement resume). >>>>> >>>>>> The code from our webmaster to update after a linked file is replaced is: >>>>> What is a "linked file"? What does this mean? >>>>> >>>>> >>>>>> 1) You need to update the playlist file with the new show. >>>>>> >>>>>> A) PARACAST FILE LIVES HERE: /usr/local/etc/paracast.m3u >>>>>> B) TECH NIGHT OWN FILE LIVES HERE: /usr/local/etc/nightowl.m3u >>>>> Given that the file names here match the file names in 3) (except the >>>>> m3u/cfg file extension), I'm going to guess that those are play lists >>>>> that then are being streamed. >>>>> >>>>> >>>>>> 2) Shut down/restart icecast. (there may be ways of not having to restart the stream, but it's beyond me) >>>>>> >>>>>> A) RUN THIS COMMAND: ps -C icecast >>>>>> B) Get the PID # that is shown for icecast >>>>>> C) RUN THIS COMMAND (where PID# is from above): kill PID# >>>>>> D) RUN THIS COMMAND: /usr/bin/icecast -c /etc/icecast.xml -b >>>>>> E) You MIGHT have to hit CTRL-C after that last step to return to prompt. >>>>> This is most certainly NOT necessary. What would make you think that you >>>>> need to do this? >>>>> Also why are you not using an init script? >>>>> >>>>> >>>>>> 3) Restart icegenerator (this is what serves the mp3 files to icecast) >>>>>> >>>>>> A) RUN THIS COMMAND: /usr/local/bin/icegenerator -f /usr/local/etc/paracast.cfg >>>>>> B) RUN THIS COMMAND: /usr/local/bin/icegenerator -f /usr/local/etc/nightowl.cfg >>>>>> >>>>>> So what am I missing? Can we make this dynamic? >>>>> I'm not familiar with Icegenerator. >>>>> Have you tried reading its documentation? >>>>> http://www.becrux.com/index.php?page=projects&name=icegenerator >>>>> >>>>> If that doesn't fit your bill you could switch to a different source >>>>> client that's capable to reload its play list dynamically. That might be >>>>> e.g. ez-stream, but there are many. >>>>> >>>>> >>>>> Cheers >>>>> >>>>> Thomas >>>>> >>>>> >>>>>>> On Sep 25, 2014, at 11:56 PM, Thomas B. R?cker <thomas at ruecker.fi> wrote: >>>>>>> >>>>>>> On 09/26/2014 12:39 AM, Gene Steinberg wrote: >>>>>>>> So I have a new Icecast setup with two channels, each of which carries a link to MP3 files. >>>>>>> Icecast is intended for live streaming, not for serving static files. >>>>>>> Which of both are you doing here? >>>>>>> >>>>>>> >>>>>>>> Whenever I update the .m3u file to reflect a changed link, I have to restart Icecast and the Icegenerator to make it recognize the change. >>>>>>> Where do you update a m3u file? Icecast generates dynamic m3u files for >>>>>>> streams, so creating your own is usually not necessary. >>>>>>> Or is this something in your source client side (Icegenerator?). >>>>>>> >>>>>>> Cheers >>>>>>> >>>>>>> Thomas >>>>>>> >>>>>>> > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast