similar to: icecast-2.3.2-kh17 versus icecast-2.3.2

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

System: Icecast 2.4.1 and 2.4.2, OS: CentOS 6.6 x64 Tried to install icecast using following two different methods described in these links: (1) http://www.ukhost4u.co.uk/blog/538/install-icecast-2-centos-6-server/ (2) https://www.servint.net/university/article/taking-the-chill-out-of-installing-icecast/ Both of these resulted in working and stable icecast, but without the possibility of url

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

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

Hi all ! Le mardi 8 d?cembre 2009 05:36:53, Jussi Kukkonen a ?crit : > > The valgrind output seems to indicate a leak in libxml2, I'm gonna try > > to see if this is linked to the way the icecast or libxml package is > > compiled/patched in debian, but I'm not too familiar with this kind of > > problems, so if you have something to say about this issue, I'd

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:

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:

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.

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: > >

On 08/12/09 20:44, Jussi Kukkonen wrote: > I'm not a icecast developer so I have very little idea what the code in > question does or how to test it. As a matter of fact I don't even have a > build environment (or time) available here, this is why I didn't send a > patch. > > But since you asked, attached are the missing frees for icecast2_2.3.2-4 > in a totally

(I'm aware that this patch is not likely to be accepted in the upstream source because Icecast doesn't really support MP3, but I thought it worthwhile to send it here in case anyone wishes to modify their local source with it.) Background: Icecast does not make any attempt to demarcate the boundaries between MP3 frames, and when a listening client connects to the server it generally

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, 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. I have also patched the icecast-2.1-trunk version (patch not published yet, needs work to extract) to enable fallback of

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 very high CPU usage for icecast 98-99%. The system I'm running is an Intel Celeron

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 09/12/2009 16:59, Romain Beauxis wrote: > Hi ! > > Le mardi 8 d?cembre 2009 19:59:23, Karl Heyes a ?crit : >>> But since you asked, attached are the missing frees for icecast2_2.3.2-4 >>> in a totally untested drive-by-patching manner. Like I said the -kh17 I >>> also happened to have did not have this specific code at all and the >>>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today we became aware of a bug in the Icecast code handling source client URL-authentication and are releasing a security fix. The bug was discovered by Juliane Holzt, who we'd like to thank for bringing this to our attention and providing us with further details. Affected Icecast versions: 2.3.3(first release with stream_auth) 2.4.0 2.4.1 Fix

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today we became aware of a bug in the Icecast code handling source client URL-authentication and are releasing a security fix. The bug was discovered by Juliane Holzt, who we'd like to thank for bringing this to our attention and providing us with further details. Affected Icecast versions: 2.3.3(first release with stream_auth) 2.4.0 2.4.1 Fix

Hi all, The URL authentication is great for reducing the administration overhead in running one or more icecast instances for lost of mountpoints and lots of listeners. However because the URL authentication is <mount> specific you still need to create a mountpoint for each (in our case) customer. Would it be possible to have a global URL authentication section which would apply to