similar to: FW: Dumping streams to a file?

Again, forwarding to the list. Please try to reply to the list. Cheers, KJ -----Oorspronkelijk bericht----- Van: Iceuse - Kris [mailto:iceuse@wwlang.net] Verzonden: woensdag 15 september 2004 7:17 Aan: k.j.wierenga@home.nl Onderwerp: Re: [Icecast] SOURCE access logging in 2.1-trunk breaks webalizer (streaming version) Thanks, I'm very confused by this kind of lists where the answer goes to

Posting it on the mailing list for you Chris :-) KJ -----Oorspronkelijk bericht----- Van: Iceuse - Kris [mailto:iceuse@wwlang.net] Verzonden: dinsdag 14 september 2004 16:49 Aan: Klaas Jan Wierenga Onderwerp: Re: [Icecast] SOURCE access logging in 2.1-trunk breaks webalizer (streaming version) Hello, Yes, that's something which is making trouble with webalizer stats... when I made this

Do you mean you can relay within a single icecast server instance? So the relay is running on the same icecast process from which it is relaying a stream? KJ -----Oorspronkelijk bericht----- Van: Karl Heyes [mailto:karl@xiph.org] Verzonden: maandag 15 november 2004 22:18 Aan: Klaas Jan Wierenga CC: icecast Onderwerp: Re: FW: [Icecast] Multi-Level Fallbacks On Mon, 2004-11-15 at 20:36, Klaas

Thanks for the status on the trunk version. I'll give the trunk version a whirl and start using it heavily :-) and report back if there are any problems. Cheers, KJ > > Van: Karl Heyes <karl@xiph.org> > Aan: Klaas Jan Wierenga <k.j.wierenga@home.nl> > CC: icecast <icecast@xiph.org> > Datum: di 7 sep 04, 19:55 > Onderwerp: Re: [Icecast] fallback to static

I'm using ezstream-0.1.2 KJ -----Oorspronkelijk bericht----- Van: Joel Ebel [mailto:jbebel@ncsu.edu] Verzonden: donderdag 3 februari 2005 21:05 Aan: Klaas Jan Wierenga Onderwerp: Re: [Icecast] Stream drops during handoff. Suggestions? Thanks. I'll have to try that. I wonder why ezstream would ever stop sending data for that long though. What version of ezstream are you running? Joel

Karl, I've managed to patch up my branch of Icecast to do the batching. Checked everything with valgrind and tested it extensively. It looks good. Tcpdump now shows nice size frames (mostly 1400 bytes). Any reason why you're not settings the MTU to something closer to 1500? Many thanks for your help, KJ -----Oorspronkelijk bericht----- Van: Karl Heyes [mailto:karl@xiph.org] Verzonden:

Karl, It would certainly be a useful feature for me and I guess others. The current solution with ezstream works but listeners all end up at the same (current) point in the mp3 file. With the mp3 file as a fallback each individual listener would want to start hearing it from the start. This might be more difficult to implement with the single-q that is in the current trunk code, I don't know.

Hi Karl, Thanks for your info. I have a standard Icecast-2.2 release with a few local patches. I'm a little apprehesive to apply my patches to the kh14 branch, so I'd rather patch my branch with the changes related to batched reads from the kh branch. I've looked at your code to see if I could spot the changes related to batching reads. So far I have not been able to find where

Please post to the mailing list the next time Ralf. I'm not using yp directory listings, but I can guess why it is not working. You're probably missing the libcurl.so library in your chroot jail directories. Here's the listing of files I have in the chroot jail: -----%< cut here > ls -R .: admin etc lib opt usr var web ./admin: listclients.xsl listmounts.xsl

Hi Geoff, Thanks, that sounds like a good idea. I've just tried it and of course it works. Then I discovered that when the original source is not connected icecast doesn't fall through to the fallback mount. Is this a known problem? KJ > > Van: Geoff Shang <gshang@pacific.net.au> > Aan: Klaas Jan Wierenga <k.j.wierenga@home.nl> > CC: icecast@xiph.org > Datum:

In my case that's not needed, but yes it would be really nice if all mount options could be retrieved from the database using an authenticated URL. KJ Stefan de Konink wrote: > On Fri, 8 Sep 2006, Klaas Jan Wierenga wrote: > > >> I guess if the <authentication type="url> section could be used as a >> top-level tag (instead of as a sub-tag of

Care to shed some light on this? I have about 10 IPs that are at my disposal and 3 I've been keeping for spares and whatnot. Though binding them is a little beyond me. TIA Justin On 6/22/05, Klaas Jan Wierenga <k.j.wierenga@home.nl> wrote: > > Hi, > > You can if your machine is assigned two IP addresses. Then you can bind the > webserver to port 80 on the first

I'm curious about why you would want to run Icecast on port 80. Geoff Justin Bot wrote: >Care to shed some light on this? I have about 10 IPs that are at my >disposal and 3 I've been keeping for spares and whatnot. Though >binding them is a little beyond me. > >TIA > >Justin > >On 6/22/05, Klaas Jan Wierenga <k.j.wierenga@home.nl> wrote: > >

Hi, I've been using icecast-2.3.1 for some time now and it is really working well for me, solid as a rock (no crashes) and running 100's of streams and 1000's of listeners, but in order to support authentication and have easier configuration I want to start using the url authentication (esp. the stream_auth) and mount-name wildcards that are supported by icecast-2.3.2-kh17.

Hi all, I'm running an Icecast-2.2 server with at peak times some 50 sources and 500 concurrent listeners all using low-bitrate 16kpbs streams. I'm experiencing some connection losses at these peak times ("Client connection died" message in error.log). The machine running Icecast has a 100Mbit connection to the internet. It is a Celeron 2.4Ghz machine with 1Gbyte of main

Hi all, I was wondering why there is a timeout (100msec) in the _acception_connection function (icecast/src/connection.c) where it calls the util_timed_wait_for_fd. To me this seems to incur unecessary load on the machine on which the icecast server runs, since each time the timeout expires some more user time is used up by the process. In my particular setup I run an icecast server 24/7, but

Klaas Jan Wierenga wrote: > Hi Henri and others, > > Very interesting post about TCP_CORK. I would be very interested in having > it applied in the next version of Icecast. I'd be more interested in some figures to show there being a benefit, most examples talk about HTTP servers with short lived connections where sendfile(2) is used. > For low-bitrate streams the problem

On Tue, 2004-09-07 at 17:54, Klaas Jan Wierenga wrote: > Karl, > > It would certainly be a useful feature for me and I guess others. The > current solution with ezstream works but listeners all end up at the > same (current) point in the mp3 file. With the mp3 file as a fallback > each individual listener would want to start hearing it from the > start. This might be more

On Mon, 2004-11-15 at 20:36, Klaas Jan Wierenga wrote: > Hi, > > I have used the SVN icecast-2.1-trunk version in my production system at > http://audioserver.nl for 2 months now without problems. The fallbacks work > fine as long as you make sure that the format (sampling frequency and > bitrate) of the mount and it's fallback match. samplerate and channels are the main

On Mon, 2005-03-07 at 22:01, Klaas Jan Wierenga wrote: > Hi all, > > I have an icecast setup with 20+ sources. During peak times some 20 sources > will be connected with a total of some 250 listeners more-or-less equally > divided over the 20 sources. All streams are running at a measly 16 kbps. > There is enough bandwidth to/from the server. During these peak times I see >