From lion at lion.leolix.org  Mon Dec  1 22:25:21 2014
From: lion at lion.leolix.org (Philipp Schafft)
Date: Mon, 01 Dec 2014 22:25:21 +0000
Subject: [Icecast] Metadata configurablity in Icecast
In-Reply-To: <alpine.DEB.2.02.1411211831420.3835@voldemort.home>
References: <alpine.DEB.2.02.1411211606280.3835@voldemort.home>
	<546F53C7.2010902@ruecker.fi>
	<alpine.DEB.2.02.1411211703250.3835@voldemort.home>
	<20141121155953.E5AC212CFE@grassland.keep-cool.org>
	<alpine.DEB.2.02.1411211831420.3835@voldemort.home>
Message-ID: <20141201222524.EC88312CFE@grassland.keep-cool.org>

reflum,

On Fri, 2014-11-21 at 18:34 +0200, Geoff Shang wrote:
> On Fri, 21 Nov 2014, Philipp Schafft wrote:
> 
> > What is your schedule? How fast do you need it? Could we target a fix
> > for in about a week?
> 
> Sorry, I didn't mean to cause a panic.

Oh, don't worry.

> I don't have an immediate need for this feature.  I know others do, or at 
> least might, and have always felt this should be configurable ever since 
> it was first implemented.  I've never run an affected version in 
> production so it has never affected me, but with the recent security 
> fixes making me think about it and the metadata thing having been
>   mentioned a few times lately, I finally spoke up.

I think I understand.

I commited a huge change to the authentication stuff in Icecast that
nearly completely replaced it. This replaces all the <*-username> and
<*-password> and some more tags with a new one we call <role>.
I think it's now possible to out of the box configure what you were
talking about. You could also define a new role that is just for
metadata updates and has no other rights.

The update is in trunk right now and will be included in the next
release (2.4.2). I would love to have some more testers on this. If you
are interested to help a bit with that and test your specific case I
would love to work with you.

To everyone who got curious what <role> may be:
It's a new way to define *any* kind of authentication in Icecast. It
allows to add 'roles' which can have fine grade configured access
rights. Another big pro of the new concept is that there is no
difference between per mount, default mount and global configuration. It
got an uniform interface.

Will Icecast 2.4.2 stop reading pre-2.4.2 config files because of this
change? No! Nor there are any plans to remove support for the old way.
No need to worry!

Have a nice evening!

-- 
Philipp.
 (Rah of PH2)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141201/a26ce1ef/attachment.sig>

From lion at lion.leolix.org  Mon Dec  1 23:52:35 2014
From: lion at lion.leolix.org (Philipp Schafft)
Date: Mon, 01 Dec 2014 23:52:35 +0000
Subject: [Icecast] Multiple Instances of Icecast???/
In-Reply-To: <m5innu$1ol$2@ger.gmane.org>
References: <m5innu$1ol$2@ger.gmane.org>
Message-ID: <20141201235238.2271412CFE@grassland.keep-cool.org>

reflum,

On Mon, 2014-12-01 at 21:48 +0000, Dean Sauer wrote:
> In tracking an issue, see posts in re sources being dropped...
> 
> I've found that there are MULTIPLE INSTANCES of icecast running...???
> 
> example:
> 
> top - 16:43:51 up 45 days, 10:25,  0 users,  load average: 0.45, 0.31, 
> 0.17
> [...]

Have you set top to display threads instead of processes?
Do you use <on-connect>/<on-disconnect>?


> Feeds are still reachable, and audio plays... but in the past multiple 
> instances of icecast has been shown to be an issue 
> 
> 
> Is there some reason that this is spawning new instances?????

No. It doesn't make sense nor is there any code in current or old
icecast versions that could do that.


> IC V2.3.2 (We are using that for reasons I've stated here already, 
> thanks.)
> 
> Host: Ubuntu 12.04 64 2GB RAM/2GB Swap, OVz VM VPS setup
> 
> Ideas????

Calming down a bit, then answering my questions.

-- 
Philipp.
 (Rah of PH2)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141201/49adb6ea/attachment.sig>

From lion at lion.leolix.org  Tue Dec  2 00:05:27 2014
From: lion at lion.leolix.org (Philipp Schafft)
Date: Tue, 02 Dec 2014 00:05:27 +0000
Subject: [Icecast] Metadata configurablity in Icecast
In-Reply-To: <m5iq2n$1ol$4@ger.gmane.org>
References: <alpine.DEB.2.02.1411211606280.3835@voldemort.home>
	<546F53C7.2010902@ruecker.fi>
	<alpine.DEB.2.02.1411211703250.3835@voldemort.home>
	<20141121155953.E5AC212CFE@grassland.keep-cool.org>
	<m5iq2n$1ol$4@ger.gmane.org>
Message-ID: <20141202000530.3278212CFE@grassland.keep-cool.org>

reflum,

On Mon, 2014-12-01 at 22:28 +0000, Dean Sauer wrote:
> On Fri, 21 Nov 2014 15:59:42 +0000, Philipp Schafft wrote:
> 
> > Also: would it be ok for you to have a global user that is allowed to do
> > that or does it need to be the source user or does it need to be any
> > source user (anyone allowed to stream to that mountpoint)?
> 
> Since I am likely the source case of this request...
> 
> A global user, other than the existing one setup for sources??
> 
> NO. I don't wish to give out any more information to sources other than:
> 
> server URL/IP
> mountpoint name
> 
> Setup darkice as follows... with the above... 
> 
> That's all they get.
> 
> If I specify specific credentials per mountpoint then ONLY THOSE *AND* 
> ADMIN should be able to send metadata.

As I told in the other mail on this thread with 2.4.2 you can set the
right to do so on every role. This includes mount specific roles.


> I actually like the idea of white listing IP's as well...
>  
> > That is a very important question to answer the above!
> > 
> > Thank you and have a good evening!
> 
> I am in no rush, as 2.3.2 is the only version in the repos for my distro, 
> and I don't compile, ever, never, ever, never. (I have enough headaches 
> to deal with already without self inflicted ones.) 
> 
> We won't upgrade past 2.3.2 till this is resolved in our favor, or not at 
> all if a choice is made to forgo this option. This option is more 
> important than the security, and I am not giving out admin credentials to 
> any one.

I'm sorry to say so, but if you don't care about security at all you can
also just publish your admin password.


Current trunk (that will be 2.4.2) contains what you need. I would be
happy to see you on IRC or drop me a mail offering some help with
testing the changes.

Have a nice evening!

-- 
Philipp.
 (Rah of PH2)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141202/c6b52525/attachment.sig>

From thomas at ruecker.fi  Tue Dec  2 00:08:00 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Tue, 02 Dec 2014 00:08:00 +0000
Subject: [Icecast] Pyhton Class/library for Icecast 2.32 Stats and other
 info access?
In-Reply-To: <m5io2c$1ol$3@ger.gmane.org>
References: <m45nrs$r0g$1@ger.gmane.org>	<CAFoW9oxWrcyt=p7HgYXKYyRUfvwAdBxzzZp=MStUBzXipby0pg@mail.gmail.com>
	<m5io2c$1ol$3@ger.gmane.org>
Message-ID: <547D02E0.1030203@ruecker.fi>

On 12/01/2014 09:54 PM, Dean Sauer wrote:
> On Fri, 14 Nov 2014 21:43:16 +0100, genocid3 wrote:
>
>> Hi, if i am not mistaken 2.4 has a servlet which provides json output
>> for active mounts and stats.
>>
>> You can check it out at http://your host:8000/status-json.xsl
>>
>> Just upgrade your version and you should be fine.
>>
> Thanks, but anything past 2.3.2

You could just use the two XSLT files that enable this with your 2.3.2
instance.
It's an untested combination and I won't support it beyond pointing it
out, but you could just try it out.

The two files are:
xml2json.xslt
status-json.xslt
Make sure to get them from 2.4.1, there was a bug in 2.4.0 that
malformed the JSON output.
Just throw them in the web-root and you're done.


TBR



From abitar.com at gmail.com  Tue Dec  2 02:33:53 2014
From: abitar.com at gmail.com (David Saunders)
Date: Mon, 1 Dec 2014 21:33:53 -0500
Subject: [Icecast] Metadata configurablity in Icecast
In-Reply-To: <20141202000530.3278212CFE@grassland.keep-cool.org>
References: <alpine.DEB.2.02.1411211606280.3835@voldemort.home>
	<546F53C7.2010902@ruecker.fi>
	<alpine.DEB.2.02.1411211703250.3835@voldemort.home>
	<20141121155953.E5AC212CFE@grassland.keep-cool.org>
	<m5iq2n$1ol$4@ger.gmane.org>
	<20141202000530.3278212CFE@grassland.keep-cool.org>
Message-ID: <CAOjZz+=7BM7nHYPf15CffhDzr+QsHGo5pBmGoFD4RY7gAzubZQ@mail.gmail.com>

I been monitoring metadata and connections statistics by a polling the
server and recording the information require.  Including the current
Metadata.,  I ended up polling on a min bases and the radion stations
station that use use been happy with the information for past couple
years.  This is via the server status page. I like to present each of our
customers with listeners counts, times listen, how long a listen has been
listing, and how many unique listeners. And for other they
need unique tags,

I event per request set up means of putting out custom meta data that is
diferent from the content stream that is blocked cause of DMC concerns.

 Its a real pain to present it in a useable form.  But I also found out
different stations have different needs .and its all based on the contracts
they have.

 IT can be done without any modifications.

:)






On Mon, Dec 1, 2014 at 7:05 PM, Philipp Schafft <lion at lion.leolix.org>
wrote:

> reflum,
>
> On Mon, 2014-12-01 at 22:28 +0000, Dean Sauer wrote:
> > On Fri, 21 Nov 2014 15:59:42 +0000, Philipp Schafft wrote:
> >
> > > Also: would it be ok for you to have a global user that is allowed to
> do
> > > that or does it need to be the source user or does it need to be any
> > > source user (anyone allowed to stream to that mountpoint)?
> >
> > Since I am likely the source case of this request...
> >
> > A global user, other than the existing one setup for sources??
> >
> > NO. I don't wish to give out any more information to sources other than:
> >
> > server URL/IP
> > mountpoint name
> >
> > Setup darkice as follows... with the above...
> >
> > That's all they get.
> >
> > If I specify specific credentials per mountpoint then ONLY THOSE *AND*
> > ADMIN should be able to send metadata.
>
> As I told in the other mail on this thread with 2.4.2 you can set the
> right to do so on every role. This includes mount specific roles.
>
>
> > I actually like the idea of white listing IP's as well...
> >
> > > That is a very important question to answer the above!
> > >
> > > Thank you and have a good evening!
> >
> > I am in no rush, as 2.3.2 is the only version in the repos for my distro,
> > and I don't compile, ever, never, ever, never. (I have enough headaches
> > to deal with already without self inflicted ones.)
> >
> > We won't upgrade past 2.3.2 till this is resolved in our favor, or not at
> > all if a choice is made to forgo this option. This option is more
> > important than the security, and I am not giving out admin credentials to
> > any one.
>
> I'm sorry to say so, but if you don't care about security at all you can
> also just publish your admin password.
>
>
> Current trunk (that will be 2.4.2) contains what you need. I would be
> happy to see you on IRC or drop me a mail offering some help with
> testing the changes.
>
> Have a nice evening!
>
> --
> Philipp.
>  (Rah of PH2)
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141201/e7f9fabf/attachment.htm>

From dtouch3d at gmail.com  Sun Dec 14 16:23:20 2014
From: dtouch3d at gmail.com (dtouch3d completely)
Date: Sun, 14 Dec 2014 18:23:20 +0200
Subject: [Icecast] Icecast AAC FLV Container
Message-ID: <CAC8Of=TFLe-9WxqfbejM6P4C7Hr4Gmi=Ao4hdB9umim+8c7iDA@mail.gmail.com>

Hello,

I am using Icecast v2.4.1 to to stream AAC audio to web clients through
jPlayer. If HTML5 is not supported then it uses Flash Player.

The problem is that Flash player does not play AAC streams as is, and from
a quick google search someonw suggested I append "?type=.flv" to the url. I
cannot make it work though as whatever I request, I get a response with
mime type "audio/aac". For example (working links):

curl "http://148.251.184.14:18002/chr_80s?type=.flv
<http://s1.chromaradio.com:18002/chr_80s?type=.flv>" -o /dev/null -D -

and

curl "http://148.251.184.14:18002/chr_80s
<http://s1.chromaradio.com:18002/chr_80s?type=.flv>" -o /dev/null -D -

returns mime type "audio/aac".

Now I remember that I got it to work some time ago, probably with an older
icecast version, and I remember that it was working as expected, and with
the extra string at the end I would get mime type "video-x-flv". Does
anyone have an idea about the problem ? Also, can anyone point me to the
documentation about the type=* option ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141214/261ad76e/attachment.htm>

From thomas at ruecker.fi  Sun Dec 14 16:34:35 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Sun, 14 Dec 2014 16:34:35 +0000
Subject: [Icecast] Icecast AAC FLV Container
In-Reply-To: <CAC8Of=TFLe-9WxqfbejM6P4C7Hr4Gmi=Ao4hdB9umim+8c7iDA@mail.gmail.com>
References: <CAC8Of=TFLe-9WxqfbejM6P4C7Hr4Gmi=Ao4hdB9umim+8c7iDA@mail.gmail.com>
Message-ID: <548DBC1B.1030007@ruecker.fi>

Hi,

On 12/14/2014 04:23 PM, dtouch3d completely wrote:
> I am using Icecast v2.4.1 to to stream AAC audio to web clients
> through jPlayer. If HTML5 is not supported then it uses Flash Player.
>
> The problem is that Flash player does not play AAC streams as is, and
> from a quick google search someonw suggested I append "?type=.flv" to
> the url. I cannot make it work though as whatever I request, I get a
> response with mime type "audio/aac".

The FLV hack only exists in the KH version maintained by Karl.

In case of missing <audio> support, I'd personally recommend to fall
back to something like the Muses player:
https://www.muses.org/
It supports AAC, if you must use AAC.

In a world where Flash is finally going away, I don't think there is a
reason for us to support the FLV hack, especially as the above
workaround exists. Muses is even open source!

HTH & Cheers

Thomas


From dtouch3d at gmail.com  Sun Dec 14 17:06:38 2014
From: dtouch3d at gmail.com (dtouch3d completely)
Date: Sun, 14 Dec 2014 19:06:38 +0200
Subject: [Icecast] Icecast AAC FLV Container
In-Reply-To: <548DBC1B.1030007@ruecker.fi>
References: <CAC8Of=TFLe-9WxqfbejM6P4C7Hr4Gmi=Ao4hdB9umim+8c7iDA@mail.gmail.com>
	<548DBC1B.1030007@ruecker.fi>
Message-ID: <CAC8Of=Q_uEJ854wb_wdOOsfe3jOmERHRjgrU-=2h9PTheWydRQ@mail.gmail.com>

Thanks a lot. Indeed with Flash going away there is no reason for hacks. I
will give Muses a try.

On Sun, Dec 14, 2014 at 6:34 PM, "Thomas B. R?cker" <thomas at ruecker.fi>
wrote:
>
> Hi,
>
> On 12/14/2014 04:23 PM, dtouch3d completely wrote:
> > I am using Icecast v2.4.1 to to stream AAC audio to web clients
> > through jPlayer. If HTML5 is not supported then it uses Flash Player.
> >
> > The problem is that Flash player does not play AAC streams as is, and
> > from a quick google search someonw suggested I append "?type=.flv" to
> > the url. I cannot make it work though as whatever I request, I get a
> > response with mime type "audio/aac".
>
> The FLV hack only exists in the KH version maintained by Karl.
>
> In case of missing <audio> support, I'd personally recommend to fall
> back to something like the Muses player:
> https://www.muses.org/
> It supports AAC, if you must use AAC.
>
> In a world where Flash is finally going away, I don't think there is a
> reason for us to support the FLV hack, especially as the above
> workaround exists. Muses is even open source!
>
> HTH & Cheers
>
> Thomas
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141214/3c2d593a/attachment.htm>

From thomas at ruecker.fi  Sun Dec 14 17:55:59 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Sun, 14 Dec 2014 17:55:59 +0000
Subject: [Icecast] [Icecast-dev]  Icecast 2.4.1 release
In-Reply-To: <546DB270.8090301@ruecker.fi>
References: <546DB270.8090301@ruecker.fi>
Message-ID: <548DCF2F.6000307@ruecker.fi>

Hi again!

If you haven't updated to 2.4.1 yet, now you have even less excuses.
Read below!

On 11/20/2014 09:20 AM, "Thomas B. R?cker" wrote:
> This is to announce the release of Icecast 2.4.1.
[?]
> Soon I'll also update the OBS repositories from 2.4.0 to 2.4.1:
> https://build.opensuse.org/package/show?package=icecast&project=home%3Adm8tbr
> The package repositories are here:
> http://download.opensuse.org/repositories/home:/dm8tbr/

Sadly it took me quite a while to figure out some issues introduced by
our new documentation directory layout. But I finally have things
working. Some people already tried out the test packages I had (where
docs were still "broken") and didn't report any problems. So go ahead to
the URLs above and add the matching repository to your distribution.

As a bonus: Those packages should now all be built with openSSL support
enabled.

While the packages don't go through extensive testing, they should work
fine, please report any issues you encounter to the Icecast mailing list
or me directly.

Cheers

Thomas



From daelynn.baudais at shaw.ca  Thu Dec 18 15:19:51 2014
From: daelynn.baudais at shaw.ca (Daelynn Baudais)
Date: Thu, 18 Dec 2014 08:19:51 -0700
Subject: [Icecast] Icecast Over ssl
Message-ID: <016f01d01ad6$12062320$36126960$@shaw.ca>

Hi,

 

Can the Icecast stream be served over an ssl (https) connection?

If so, can you please tell me how to accomplish this?

 

Thanks,

Daelynn.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141218/185fa162/attachment.htm>

From xoneca+icecast at gmail.com  Thu Dec 18 20:29:21 2014
From: xoneca+icecast at gmail.com (Xabier Oneca -- xOneca)
Date: Thu, 18 Dec 2014 21:29:21 +0100
Subject: [Icecast] Icecast Over ssl
In-Reply-To: <016f01d01ad6$12062320$36126960$@shaw.ca>
References: <016f01d01ad6$12062320$36126960$@shaw.ca>
Message-ID: <CACkgH73GwbW=x_hiDdmmKkwLJriTQWTjZ435aHnVCPX7qvw-Lg@mail.gmail.com>

Hello Daelynn,

Icecast doesn't have SSL support, but you can try with stunnel. I haven't
tried it with Icecast, but it should work. I have stunnel working with
other services, though, and works like a charm!

HTH,

Xabier Oneca_,,_
El 18/12/2014 21:15, "Daelynn Baudais" <daelynn.baudais at shaw.ca> escribi?:

> Hi,
>
>
>
> Can the Icecast stream be served over an ssl (https) connection?
>
> If so, can you please tell me how to accomplish this?
>
>
>
> Thanks,
>
> Daelynn.
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141218/1ce06bb3/attachment.htm>

From thomas at ruecker.fi  Thu Dec 18 20:33:46 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 18 Dec 2014 20:33:46 +0000
Subject: [Icecast] Icecast Over ssl
In-Reply-To: <016f01d01ad6$12062320$36126960$@shaw.ca>
References: <016f01d01ad6$12062320$36126960$@shaw.ca>
Message-ID: <54933A2A.6050402@ruecker.fi>

On 12/18/2014 03:19 PM, Daelynn Baudais wrote:
>
> Hi,
>
>  
>
> Can the Icecast stream be served over an ssl (https) connection?
>

Yes.

> If so, can you please tell me how to accomplish this?
>

http://icecast.org/docs/icecast-2.4.1/config-file.html#ports
Usually you'd set this to 8443 or 443, if the latter, then you MUST also
configure changeuser and start as root.

http://icecast.org/docs/icecast-2.4.1/config-file.html#path
Point to the certificates.

If you have further questions, please subscribe to the mailing list
before you hit reply on this email:
http://lists.xiph.org/mailman/listinfo/icecast


Cheers

Thomas


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141218/cc8337ff/attachment.htm>

From thomas at ruecker.fi  Thu Dec 18 20:34:48 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 18 Dec 2014 20:34:48 +0000
Subject: [Icecast] Icecast Over ssl
In-Reply-To: <CACkgH73GwbW=x_hiDdmmKkwLJriTQWTjZ435aHnVCPX7qvw-Lg@mail.gmail.com>
References: <016f01d01ad6$12062320$36126960$@shaw.ca>
	<CACkgH73GwbW=x_hiDdmmKkwLJriTQWTjZ435aHnVCPX7qvw-Lg@mail.gmail.com>
Message-ID: <54933A68.2000409@ruecker.fi>

On 12/18/2014 08:29 PM, Xabier Oneca -- xOneca wrote:
>
> Hello Daelynn,
>
> Icecast doesn't have SSL support, but you can try with stunnel. I
> haven't tried it with Icecast, but it should work. I have stunnel
> working with other services, though, and works like a charm!
>
That's bull...
see my other reply.

TBR
>
> HTH,
>
> Xabier Oneca_,,_
>
> El 18/12/2014 21:15, "Daelynn Baudais" <daelynn.baudais at shaw.ca
> <mailto:daelynn.baudais at shaw.ca>> escribi?:
>
>     Hi,
>
>      
>
>     Can the Icecast stream be served over an ssl (https) connection?
>
>     If so, can you please tell me how to accomplish this?
>
>      
>
>     Thanks,
>
>     Daelynn.
>
>
>     _______________________________________________
>     Icecast mailing list
>     Icecast at xiph.org <mailto: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



From thomas at ruecker.fi  Thu Dec 18 20:37:14 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 18 Dec 2014 20:37:14 +0000
Subject: [Icecast] Icecast Over ssl
In-Reply-To: <54933A2A.6050402@ruecker.fi>
References: <016f01d01ad6$12062320$36126960$@shaw.ca>
	<54933A2A.6050402@ruecker.fi>
Message-ID: <54933AFA.8010502@ruecker.fi>

On 12/18/2014 08:33 PM, "Thomas B. R?cker" wrote:
> On 12/18/2014 03:19 PM, Daelynn Baudais wrote:
>>
>> Hi,
>>
>>  
>>
>> Can the Icecast stream be served over an ssl (https) connection?
>>
>
> Yes.

Please note that for this to work Icecast MUST have been compiled with
openSSL support.
While some distributions don't, there are packages linked from the
webpage at http://icecast.org that have openSSL support built in.

>> If so, can you please tell me how to accomplish this?
>>
>
> http://icecast.org/docs/icecast-2.4.1/config-file.html#ports
> Usually you'd set this to 8443 or 443, if the latter, then you MUST
> also configure changeuser and start as root.
>
> http://icecast.org/docs/icecast-2.4.1/config-file.html#path
> Point to the certificates.
>
> If you have further questions, please subscribe to the mailing list
> before you hit reply on this email:
> http://lists.xiph.org/mailman/listinfo/icecast
>

Cheers

Thomas


From thomas at ruecker.fi  Thu Dec 18 21:24:58 2014
From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=)
Date: Thu, 18 Dec 2014 21:24:58 +0000
Subject: [Icecast] Icecast Over ssl
In-Reply-To: <CACkgH70L3ZhcQHmmG+zyUrEBkDvZD4XQqgyMqUS05XL7_no-wQ@mail.gmail.com>
References: <016f01d01ad6$12062320$36126960$@shaw.ca>	<CACkgH73GwbW=x_hiDdmmKkwLJriTQWTjZ435aHnVCPX7qvw-Lg@mail.gmail.com>	<54933A68.2000409@ruecker.fi>
	<CACkgH70L3ZhcQHmmG+zyUrEBkDvZD4XQqgyMqUS05XL7_no-wQ@mail.gmail.com>
Message-ID: <5493462A.9030501@ruecker.fi>

On 12/18/2014 08:54 PM, Xabier Oneca -- xOneca wrote:
>
> Hello, Thomas,
>
> El 18/12/2014 21:35, Thomas B. R?cker <thomas at ruecker.fi
> <mailto:thomas at ruecker.fi>> escribi?:
> >
> > On 12/18/2014 08:29 PM, Xabier Oneca -- xOneca wrote:
> > >
> > > Hello Daelynn,
> > >
> > > Icecast doesn't have SSL support, but you can try with stunnel. I
> > > haven't tried it with Icecast, but it should work. I have stunnel
> > > working with other services, though, and works like a charm!
> > >
> > That's bull...
> > see my other reply.
>
> Sorry! I wanted to say I didn't know it it had support. I don't know
> why I've written that! :S
>
> That's what happens by replying with my mind in other things, I suppose...
>

No worries, now you know. :-)


> > TBR
> > >
> > > HTH,
> > >
> > > Xabier Oneca_,,_
> > >
> > > El 18/12/2014 21:15, "Daelynn Baudais" <daelynn.baudais at shaw.ca
> <mailto:daelynn.baudais at shaw.ca>
> > > <mailto:daelynn.baudais at shaw.ca <mailto:daelynn.baudais at shaw.ca>>>
> escribi?:
> > >
> > >     Hi,
> > >
> > >
> > >
> > >     Can the Icecast stream be served over an ssl (https) connection?
> > >
> > >     If so, can you please tell me how to accomplish this?
> > >
> > >
> > >
> > >     Thanks,
> > >
> > >     Daelynn.
>
> Sorry again and cheers!
>
> Xabier Oneca_,,_
>

Don't sweat it, just wanted to be sure people don't pick up the stunnel
idea as it's a rather problematic workaround.

Cheers

Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141218/2d8d58da/attachment.htm>

From xoneca+icecast at gmail.com  Thu Dec 18 21:43:49 2014
From: xoneca+icecast at gmail.com (Xabier Oneca -- xOneca)
Date: Thu, 18 Dec 2014 22:43:49 +0100
Subject: [Icecast] Icecast Over ssl
In-Reply-To: <5493462A.9030501@ruecker.fi>
References: <016f01d01ad6$12062320$36126960$@shaw.ca>
	<CACkgH73GwbW=x_hiDdmmKkwLJriTQWTjZ435aHnVCPX7qvw-Lg@mail.gmail.com>
	<54933A68.2000409@ruecker.fi>
	<CACkgH70L3ZhcQHmmG+zyUrEBkDvZD4XQqgyMqUS05XL7_no-wQ@mail.gmail.com>
	<5493462A.9030501@ruecker.fi>
Message-ID: <CACkgH70OmCUTynf4zVFFz71xU++nxYXFzgsQukyxuyiucUdVdA@mail.gmail.com>

Hi Thomas,

El 18/12/2014 22:25, Thomas B. R?cker <thomas at ruecker.fi> escribi?:
>
> On 12/18/2014 08:54 PM, Xabier Oneca -- xOneca wrote:
>>
>> Hello, Thomas,
>>
>> El 18/12/2014 21:35, Thomas B. R?cker <thomas at ruecker.fi> escribi?:
>> >
>> > On 12/18/2014 08:29 PM, Xabier Oneca -- xOneca wrote:
>> > >
>> > > Hello Daelynn,
>> > >
>> > > Icecast doesn't have SSL support, but you can try with stunnel. I
>> > > haven't tried it with Icecast, but it should work. I have stunnel
>> > > working with other services, though, and works like a charm!
>> > >
>> > That's bull...
>> > see my other reply.
>>
>> Sorry! I wanted to say I didn't know it it had support. I don't know why
I've written that! :S
>>
>> That's what happens by replying with my mind in other things, I
suppose...
>
>
> No worries, now you know. :-)
>
>
>
>> > TBR
>> > >
>> > > HTH,
>> > >
>> > > Xabier Oneca_,,_
>> > >
>> > > El 18/12/2014 21:15, "Daelynn Baudais" <daelynn.baudais at shaw.ca
>> > > <mailto:daelynn.baudais at shaw.ca>> escribi?:
>> > >
>> > >     Hi,
>> > >
>> > >
>> > >
>> > >     Can the Icecast stream be served over an ssl (https) connection?
>> > >
>> > >     If so, can you please tell me how to accomplish this?
>> > >
>> > >
>> > >
>> > >     Thanks,
>> > >
>> > >     Daelynn.
>>
>> Sorry again and cheers!
>>
>> Xabier Oneca_,,_
>
>
> Don't sweat it, just wanted to be sure people don't pick up the stunnel
idea as it's a rather problematic workaround.

So, Icecast + stunnel is not a good idea?

I prefer using 'native' SSL support, but when there isn't, I am very happy
using stunnel.

> Cheers
>
> Thomas

Cheers,

Xabier Oneca_,,_
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141218/54c5c32a/attachment.htm>

From thomas at ruecker.fi  Thu Dec 18 21:52:03 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 18 Dec 2014 21:52:03 +0000
Subject: [Icecast] Icecast Over ssl
In-Reply-To: <CACkgH70OmCUTynf4zVFFz71xU++nxYXFzgsQukyxuyiucUdVdA@mail.gmail.com>
References: <016f01d01ad6$12062320$36126960$@shaw.ca>	<CACkgH73GwbW=x_hiDdmmKkwLJriTQWTjZ435aHnVCPX7qvw-Lg@mail.gmail.com>	<54933A68.2000409@ruecker.fi>	<CACkgH70L3ZhcQHmmG+zyUrEBkDvZD4XQqgyMqUS05XL7_no-wQ@mail.gmail.com>	<5493462A.9030501@ruecker.fi>
	<CACkgH70OmCUTynf4zVFFz71xU++nxYXFzgsQukyxuyiucUdVdA@mail.gmail.com>
Message-ID: <54934C83.9070209@ruecker.fi>

On 12/18/2014 09:43 PM, Xabier Oneca -- xOneca wrote:
>
> Hi Thomas,
>
> El 18/12/2014 22:25, Thomas B. R?cker <thomas at ruecker.fi
> <mailto:thomas at ruecker.fi>> escribi?:
> >
> > On 12/18/2014 08:54 PM, Xabier Oneca -- xOneca wrote:
> >>
> >> Hello, Thomas,
> >>
> >> El 18/12/2014 21:35, Thomas B. R?cker <thomas at ruecker.fi
> <mailto:thomas at ruecker.fi>> escribi?:
> >> >
> >> > On 12/18/2014 08:29 PM, Xabier Oneca -- xOneca wrote:
> >> > >
> >> > > Hello Daelynn,
> >> > >
> >> > > Icecast doesn't have SSL support, but you can try with stunnel. I
> >> > > haven't tried it with Icecast, but it should work. I have stunnel
> >> > > working with other services, though, and works like a charm!
> >> > >
> >> > That's bull...
> >> > see my other reply.
> >>
> >> Sorry! I wanted to say I didn't know it it had support. I don't
> know why I've written that! :S
> >>
> >> That's what happens by replying with my mind in other things, I
> suppose...
> >
> >
> > No worries, now you know. :-)
> >
> >
> >
> >> > TBR
> >> > >
> >> > > HTH,
> >> > >
> >> > > Xabier Oneca_,,_
> >> > >
> >> > > El 18/12/2014 21:15, "Daelynn Baudais" <daelynn.baudais at shaw.ca
> <mailto:daelynn.baudais at shaw.ca>
> >> > > <mailto:daelynn.baudais at shaw.ca
> <mailto:daelynn.baudais at shaw.ca>>> escribi?:
> >> > >
> >> > >     Hi,
> >> > >
> >> > >
> >> > >
> >> > >     Can the Icecast stream be served over an ssl (https)
> connection?
> >> > >
> >> > >     If so, can you please tell me how to accomplish this?
> >> > >
> >> > >
> >> > >
> >> > >     Thanks,
> >> > >
> >> > >     Daelynn.
> >>
> >> Sorry again and cheers!
> >>
> >> Xabier Oneca_,,_
> >
> >
> > Don't sweat it, just wanted to be sure people don't pick up the
> stunnel idea as it's a rather problematic workaround.
>
> So, Icecast + stunnel is not a good idea?
>

For starters you lose the ability to see the IP of your clients in Icecast.
Also all dynamic content likely will generate for something different
(although the same problem might currently exist with Icecast, it would
be reasonable to fix as Icecast is aware of a connection on a SSL socket
as opposed to plain TCP).

> I prefer using 'native' SSL support, but when there isn't, I am very
> happy using stunnel.
>
Yes, it is OK as a work-around. It comes at certain inconveniences that
need to be weighed.


Cheers

Thomas



From xoneca+icecast at gmail.com  Thu Dec 18 22:24:37 2014
From: xoneca+icecast at gmail.com (Xabier Oneca -- xOneca)
Date: Thu, 18 Dec 2014 23:24:37 +0100
Subject: [Icecast] Icecast Over ssl
In-Reply-To: <54934C83.9070209@ruecker.fi>
References: <016f01d01ad6$12062320$36126960$@shaw.ca>
	<CACkgH73GwbW=x_hiDdmmKkwLJriTQWTjZ435aHnVCPX7qvw-Lg@mail.gmail.com>
	<54933A68.2000409@ruecker.fi>
	<CACkgH70L3ZhcQHmmG+zyUrEBkDvZD4XQqgyMqUS05XL7_no-wQ@mail.gmail.com>
	<5493462A.9030501@ruecker.fi>
	<CACkgH70OmCUTynf4zVFFz71xU++nxYXFzgsQukyxuyiucUdVdA@mail.gmail.com>
	<54934C83.9070209@ruecker.fi>
Message-ID: <CACkgH73MSX7=NknFBHveVimhh_SMcuwCf=QnajajfR3gw_EkoA@mail.gmail.com>

Hello,

El 18/12/2014 22:52, Thomas B. R?cker <thomas at ruecker.fi> escribi?:
>
> On 12/18/2014 09:43 PM, Xabier Oneca -- xOneca wrote:
> >
> > Hi Thomas,
> >
> > El 18/12/2014 22:25, Thomas B. R?cker <thomas at ruecker.fi
> > <mailto:thomas at ruecker.fi>> escribi?:
> > >
> > > On 12/18/2014 08:54 PM, Xabier Oneca -- xOneca wrote:
> > >>
> > >> Hello, Thomas,
> > >>
> > >> El 18/12/2014 21:35, Thomas B. R?cker <thomas at ruecker.fi
> > <mailto:thomas at ruecker.fi>> escribi?:
> > >> >
> > >> > On 12/18/2014 08:29 PM, Xabier Oneca -- xOneca wrote:
> > >> > >
> > >> > > Hello Daelynn,
> > >> > >
> > >> > > Icecast doesn't have SSL support, but you can try with stunnel. I
> > >> > > haven't tried it with Icecast, but it should work. I have stunnel
> > >> > > working with other services, though, and works like a charm!
> > >> > >
> > >> > That's bull...
> > >> > see my other reply.
> > >>
> > >> Sorry! I wanted to say I didn't know it it had support. I don't
> > know why I've written that! :S
> > >>
> > >> That's what happens by replying with my mind in other things, I
> > suppose...
> > >
> > >
> > > No worries, now you know. :-)
> > >
> > >
> > >
> > >> > TBR
> > >> > >
> > >> > > HTH,
> > >> > >
> > >> > > Xabier Oneca_,,_
> > >> > >
> > >> > > El 18/12/2014 21:15, "Daelynn Baudais" <daelynn.baudais at shaw.ca
> > <mailto:daelynn.baudais at shaw.ca>
> > >> > > <mailto:daelynn.baudais at shaw.ca
> > <mailto:daelynn.baudais at shaw.ca>>> escribi?:
> > >> > >
> > >> > >     Hi,
> > >> > >
> > >> > >
> > >> > >
> > >> > >     Can the Icecast stream be served over an ssl (https)
> > connection?
> > >> > >
> > >> > >     If so, can you please tell me how to accomplish this?
> > >> > >
> > >> > >
> > >> > >
> > >> > >     Thanks,
> > >> > >
> > >> > >     Daelynn.
> > >>
> > >> Sorry again and cheers!
> > >>
> > >> Xabier Oneca_,,_
> > >
> > >
> > > Don't sweat it, just wanted to be sure people don't pick up the
> > stunnel idea as it's a rather problematic workaround.
> >
> > So, Icecast + stunnel is not a good idea?
> >
>
> For starters you lose the ability to see the IP of your clients in
Icecast.

True. Didn't think on this one.

> Also all dynamic content likely will generate for something different
> (although the same problem might currently exist with Icecast, it would
> be reasonable to fix as Icecast is aware of a connection on a SSL socket
> as opposed to plain TCP).
>
> > I prefer using 'native' SSL support, but when there isn't, I am very
> > happy using stunnel.
> >
> Yes, it is OK as a work-around. It comes at certain inconveniences that
> need to be weighed.

I don't know if there's a previous discussion about this in the list, but
this is very interesting to have.

Now that Mozilla is going to give away signed certs for free, this gains
interest.

>
> Cheers
>
> Thomas

Cheers,

Xabier Oneca_,,_
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141218/de0f2c8b/attachment.htm>

From metaledgeradio at metaledgeradio.com  Fri Dec 19 17:26:47 2014
From: metaledgeradio at metaledgeradio.com (metaledgeradio)
Date: Fri, 19 Dec 2014 09:26:47 -0800
Subject: [Icecast] Player Widget
Message-ID: <14a639520ed.d9ac757640364.4736940513435551201@metaledgeradio.com>

Looking for a player widget that will be compatible with Joomla.
 
Metal Edge Radio

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141219/3bce3405/attachment.htm>

From hoggins at radiom.fr  Fri Dec 19 19:35:48 2014
From: hoggins at radiom.fr (Hoggins!)
Date: Fri, 19 Dec 2014 20:35:48 +0100
Subject: [Icecast] Player Widget
In-Reply-To: <14a639520ed.d9ac757640364.4736940513435551201@metaledgeradio.com>
References: <14a639520ed.d9ac757640364.4736940513435551201@metaledgeradio.com>
Message-ID: <54947E14.7030403@radiom.fr>

Hello,

You should have a look at jPlayer. We don't use Joomla, but we're using
it on our website (http://radiom.fr), and it is said to have modules in
the Joomla library.

Cheers !

Le 19/12/2014 18:26, metaledgeradio a ?crit :
> Looking for a player widget that will be compatible with Joomla.
>  
> Metal Edge Radio





From lion at lion.leolix.org  Sat Dec 20 10:23:18 2014
From: lion at lion.leolix.org (Philipp Schafft)
Date: Sat, 20 Dec 2014 10:23:18 +0000
Subject: [Icecast] Multiple Instances of Icecast???/
In-Reply-To: <m64l4d$s0v$1@ger.gmane.org>
References: <m5innu$1ol$2@ger.gmane.org>
	<20141201235238.2271412CFE@grassland.keep-cool.org>
	<m64l4d$s0v$1@ger.gmane.org>
Message-ID: <20141220102322.D68C112CFE@grassland.keep-cool.org>

reflum,

On Mon, 2014-12-08 at 16:54 +0000, Dean Sauer wrote:
> On Mon, 01 Dec 2014 23:52:35 +0000, Philipp Schafft wrote:
> 
> > Have you set top to display threads instead of processes?
> 
> I rebooted, one process started, after a while... back to the insane 
> numbers of them, and even more threads.... 
> 
> below is:
> 
> top -H (all threads)
> 1509 icecast2  20   0 1840m 9568 1676 S    1  0.5   1:37.18 
> icecast2                                                                                                        
>   704 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:10.81 
> icecast2                                                                                                        
>   712 icecast2  20   0 1840m 9568 1676 S    0  0.5   4:09.60 
> icecast2                                                                                                        
>  1421 icecast2  20   0 1840m 9568 1676 S    0  0.5   3:10.65 
> icecast2                                                                                                        
>  1425 icecast2  20   0 1840m 9568 1676 S    0  0.5   4:21.34 
> icecast2                                                                                                        
>  1498 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:51.76 
> icecast2                                                                                                        
>  1510 icecast2  20   0 1840m 9568 1676 S    0  0.5   1:08.70 
> icecast2                                                                                                        
>  2813 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:00.25 
> icecast2                                                                                                        
>     1 root      20   0 23740 1220  856 S    0  0.1   0:00.14 
> init                                                                                                            
>     2 root      20   0     0    0    0 S    0  0.0   0:00.00 
> kthreadd/54931                                                                                                  
>     3 root      20   0     0    0    0 S    0  0.0   0:00.00 
> khelper/54931                                                                                                   
>   340 root      20   0 19068  912  704 S    0  0.0   0:00.10 
> cron                                                                                                            
>   362 root      20   0  6408  804  660 S    0  0.0   0:00.97 
> syslogd                                                                                                         
>   457 root      20   0 49992 2660 2056 S    0  0.1   0:00.62 
> sshd                                                                                                            
>   687 Debian-e  20   0 47484 1056  604 S    0  0.1   0:00.01 
> exim4                                                                                                           
>   695 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:29.11 
> icecast2                                                                                                        
>   700 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:32.07 
> icecast2                                                                                                        
>   702 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:21.16 
> icecast2                                                                                                        
>   705 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:02.43 
> icecast2                                                                                                        
>   706 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:08.72 
> icecast2                                                                                                        
>   707 icecast2  20   0 1840m 9568 1676 S    0  0.5   4:55.13 
> icecast2                                                                                                        
>   708 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:10.60 
> icecast2                                                                                                        
>   710 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:44.52 
> icecast2                                                                                                        
>   713 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:08.89 
> icecast2                                                                                                        
>   714 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:08.87 
> icecast2                                                                                                        
>   715 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:09.29 
> icecast2                                                                                                        
>   716 icecast2  20   0 1840m 9568 1676 S    0  0.5   3:36.53 
> icecast2                                                                                                        
>   717 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:09.75 
> icecast2                                                                                                        
>   718 icecast2  20   0 1840m 9568 1676 S    0  0.5   1:54.28 
> icecast2                                                                                                        
>  1423 icecast2  20   0 1840m 9568 1676 S    0  0.5   3:33.27 
> icecast2                                                                                                        
>  1512 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:24.15 
> icecast2                                                                                                        
>  1513 icecast2  20   0 1840m 9568 1676 S    0  0.5   0:20.83 
> icecast2                                                                                                        
>   805 icecast2  20   0 1840m 6848  128 S    0  0.3   0:00.00 
> icecast2                                                                                                        
>   808 icecast2  20   0 1840m 6900  128 S    0  0.3   0:00.00 
> icecast2                                                                                                        
>  1320 root      20   0 33944  688  396 S    0  0.0   0:02.82 
> vzctl                                                                                                           
>  1321 root      20   0 18024 1816 1328 S    0  0.1   0:00.01 
> bash                                                                                                            
>  1392 icecast2  20   0 1840m 8172  128 S    0  0.4   0:00.00 
> icecast2                                                                                                        
>  1394 icecast2  20   0 1840m 8172  128 S    0  0.4   0:00.00 
> icecast2                                                                                                        
> root at audio:/# pgrep icecast2
> 695
> 805
> 808
> 1392
> 1394
> 1405
> 1409
> root at audio:/# top 
> 
> # top   
> top - 11:45:06 up 22:16,  0 users,  load average: 0.10, 0.10, 0.12
> Tasks:  17 total,   1 running,  16 sleeping,   0 stopped,   0 zombie
> Cpu(s):  0.1%us,  0.8%sy,  0.0%ni, 98.9%id,  0.1%wa,  0.0%hi,  0.0%si,  
> 0.1%st
> Mem:   2097152k total,    82036k used,  2015116k free,        0k buffers
> Swap:  2097152k total,        0k used,  2097152k free,    50836k cached
> 
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  
> COMMAND                                                                                                         
>   695 icecast2  20   0 1840m 9588 1676 S    2  0.5  51:56.25 
> icecast2                                                                                                        
>     1 root      20   0 23740 1220  856 S    0  0.1   0:00.14 
> init                                                                                                            
>     2 root      20   0     0    0    0 S    0  0.0   0:00.00 
> kthreadd/54931                                                                                                  
>     3 root      20   0     0    0    0 S    0  0.0   0:00.00 
> khelper/54931                                                                                                   
>   340 root      20   0 19068  912  704 S    0  0.0   0:00.10 
> cron                                                                                                            
>   362 root      20   0  6408  804  660 S    0  0.0   0:00.97 
> syslogd                                                                                                         
>   457 root      20   0 49992 2660 2056 S    0  0.1   0:00.62 
> sshd                                                                                                            
>   687 Debian-e  20   0 47484 1056  604 S    0  0.1   0:00.01 
> exim4                                                                                                           
>   805 icecast2  20   0 1840m 6848  128 S    0  0.3   0:00.00 
> icecast2                                                                                                        
>   808 icecast2  20   0 1840m 6900  128 S    0  0.3   0:00.00 
> icecast2                                                                                                        
>  1320 root      20   0 33944  688  396 S    0  0.0   0:02.82 
> vzctl                                                                                                           
>  1321 root      20   0 18024 1816 1328 S    0  0.1   0:00.01 
> bash                                                                                                            
>  1392 icecast2  20   0 1840m 8172  128 S    0  0.4   0:00.00 
> icecast2                                                                                                        
>  1394 icecast2  20   0 1840m 8172  128 S    0  0.4   0:00.00 
> icecast2                                                                                                        
>  1405 icecast2  20   0 1840m 8176  128 S    0  0.4   0:00.00 
> icecast2                                                                                                        
>  1409 icecast2  20   0 1840m 8176  128 S    0  0.4   0:00.00 
> icecast2                                                                                                        
>  2820 root      20   0 17156 1196  956 R    0  0.1   0:00.00 
> top                                                                                                             
> 
> 
> 
> 
> > Do you use <on-connect>/<on-disconnect>?
> 
> each mount has a stanza like this:
> 
> <mount>
>  <mount-name>/feedMyName</mount-name>
>  <on-disconnect>/etc/icecast2/feeddown4.sh</on-disconnect>
>  <fallback-mount>/feedMyName.mp3</fallback-mount>
>  <fallback-override>1</fallback-override>
> </mount>
> 
> 
> Thus if the source drops it falls to another, which is basically an alert 
> for me.. and sends an email via my BASH script.

Does your script return?


> > No. It doesn't make sense nor is there any code in current or old
> > icecast versions that could do that.
> 
> > Calming down a bit, then answering my questions.
> 
> If there is no code to spawn it then what would be spawning it??? 

There is only code for event_exec (former: on-[dis]connect). But before
that mail you wasn't talking about using them. Icecast itself spawns
only threads beside event_exec.

we have had some major changes to that the last days and weeks.
Could you test with current trunk from git? If it still spawns processes
that aren't your script we should have a closer look at this. we plan to
do a beta as of this year and another next year. I would target that one
for a potential fix if there is still a problem.


> Drops of the sources are just not tolerable for these feeds... Especially 
> as the sources think they ARE STILL CONNECTED! Both Darkice and some 
> piece of junk wincrap programs do it, the wincrap ones especially do not 
> like this...

I don't think this is the same problem if there is any on Icecast's side
at all.

-- 
Philipp.
 (Rah of PH2)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141220/ff2e1cbc/attachment.sig>

From thomas at ruecker.fi  Fri Dec 26 21:35:34 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Fri, 26 Dec 2014 21:35:34 +0000
Subject: [Icecast] [Icecast-dev] Icecast 2.4.1 release (Windows
	Installer)
In-Reply-To: <548DCF2F.6000307@ruecker.fi>
References: <546DB270.8090301@ruecker.fi> <548DCF2F.6000307@ruecker.fi>
Message-ID: <549DD4A6.2060608@ruecker.fi>

Hi once again!

Merry whatever doesn't offend you!

I've taken the time to set up a clean automated build of Icecast for
Windows. This is on the Open Build Service instance of the OpenSUSE
folks. It is now building against a clean and up to date MinGW32
environment, maintained as part of openSUSE.

This needed some fixes to our code to build properly. Erik van
Pienbroek, of the Fedora project, was of invaluable help and spent some
hours cleaning up our MinGW32 specific code.

The last two days I've spent hours building on top of the great ground
work for a new Windows installer started by our Stephan Jauernick.
Utilizing the Nullsoft Installer framework we're able to create Windows
installers also from our Linux build environment.

I've chosen to redo the Windows release of Icecast 2.4.1, as the
original one for Windows was just the provisional Zip file. Also we're
not going to have a new stable release for the next couple of months, so
I want our Windows users to have a nice installation experience without
the need to wait long. (Spoiler: There will be a beta release during the
next few days though.)

Without further ado, here's the Windows installer:
http://downloads.xiph.org/releases/icecast/icecast_win32_2.4.1.exe

Notes:
- Not usable to upgrade older versions, you MUST back up your config XML
and uninstall any old versions before installing this version. If you
used the Zip file 2.4.0/2.4.1 builds, please don't try to install into
such a directory but delete it first, only retaining the config XML.
- Will install cleanly over itself and not overwrite existing config.
- Properly registers with the Windows software management infrastructure.
- Start menu contains items for: starting server (console window MUST
stay open), web interface and documentation.
- Supports HTTPS aka "SSL" (TLSv1 and up, really), see documentation for
details.

Things still on my ToDo list for future releases:
- Windows service installation (there is a workaround utilizing "nssm"
though)
- Uninstall option to purge also config and web files, currently
retained to enable easy reinstallation

I've done some installation and runtime testing including HTTPS and
didn't notice any problems. Actually I'm listening to a stream right now
over HTTPS. If there are any issues, please let me know if you run into
problems.

Cheers

Thomas

PS: The 2.4.1 zip file is now deprecated and shouldn't be used anymore!
Website will update shortly.



From streamfinder at gmail.com  Fri Dec 26 21:43:58 2014
From: streamfinder at gmail.com (Streamfinder)
Date: Fri, 26 Dec 2014 15:43:58 -0600
Subject: [Icecast] [Icecast-dev] Icecast 2.4.1 release (Windows
	Installer)
In-Reply-To: <549DD4A6.2060608@ruecker.fi>
References: <546DB270.8090301@ruecker.fi> <548DCF2F.6000307@ruecker.fi>
	<549DD4A6.2060608@ruecker.fi>
Message-ID: <CAB_Y3m_6bwtd_dKknaU-vBN=Yz3B8wpfRgw4CXdvWCvjrpmaJQ@mail.gmail.com>

Thomas -
Thanks for taking the time and doing this. Much appreciated
Chris C.
Windows Icecast User

On Fri, Dec 26, 2014 at 3:35 PM, "Thomas B. R?cker" <thomas at ruecker.fi>
wrote:

> Hi once again!
>
> Merry whatever doesn't offend you!
>
> I've taken the time to set up a clean automated build of Icecast for
> Windows. This is on the Open Build Service instance of the OpenSUSE
> folks. It is now building against a clean and up to date MinGW32
> environment, maintained as part of openSUSE.
>
> This needed some fixes to our code to build properly. Erik van
> Pienbroek, of the Fedora project, was of invaluable help and spent some
> hours cleaning up our MinGW32 specific code.
>
> The last two days I've spent hours building on top of the great ground
> work for a new Windows installer started by our Stephan Jauernick.
> Utilizing the Nullsoft Installer framework we're able to create Windows
> installers also from our Linux build environment.
>
> I've chosen to redo the Windows release of Icecast 2.4.1, as the
> original one for Windows was just the provisional Zip file. Also we're
> not going to have a new stable release for the next couple of months, so
> I want our Windows users to have a nice installation experience without
> the need to wait long. (Spoiler: There will be a beta release during the
> next few days though.)
>
> Without further ado, here's the Windows installer:
> http://downloads.xiph.org/releases/icecast/icecast_win32_2.4.1.exe
>
> Notes:
> - Not usable to upgrade older versions, you MUST back up your config XML
> and uninstall any old versions before installing this version. If you
> used the Zip file 2.4.0/2.4.1 builds, please don't try to install into
> such a directory but delete it first, only retaining the config XML.
> - Will install cleanly over itself and not overwrite existing config.
> - Properly registers with the Windows software management infrastructure.
> - Start menu contains items for: starting server (console window MUST
> stay open), web interface and documentation.
> - Supports HTTPS aka "SSL" (TLSv1 and up, really), see documentation for
> details.
>
> Things still on my ToDo list for future releases:
> - Windows service installation (there is a workaround utilizing "nssm"
> though)
> - Uninstall option to purge also config and web files, currently
> retained to enable easy reinstallation
>
> I've done some installation and runtime testing including HTTPS and
> didn't notice any problems. Actually I'm listening to a stream right now
> over HTTPS. If there are any issues, please let me know if you run into
> problems.
>
> Cheers
>
> Thomas
>
> PS: The 2.4.1 zip file is now deprecated and shouldn't be used anymore!
> Website will update shortly.
>
> _______________________________________________
> Icecast-dev mailing list
> Icecast-dev at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141226/f8dc5f25/attachment.htm>

From lion at lion.leolix.org  Sun Dec 28 11:29:57 2014
From: lion at lion.leolix.org (Philipp Schafft)
Date: Sun, 28 Dec 2014 11:29:57 +0000
Subject: [Icecast] bored? Become a Icecast volunteer
Message-ID: <20141228112959.29B9B12CFE@grassland.keep-cool.org>

Good morning everyone!

As some of you may already have noticed we made quite some progress
during the last few weeks. Icecast got some major updates to internal
parts. Visible to the outside are the new tags <role> and <event>.

Those changes lead to need of updating documentation. Something we have
been working on anyway. Beside documentation also testing is a topic
getting more and more important to improve stability and performance.

As the current team can hardly handle all those in-time and that will
delay releases, so we are looking for some volunteers.

There are many tasks to do. Also no programming skills required! There
is something useful to do for _everyone_ who wants to help and any time
amount you want to spend!

If you are interested just reply to this mail or join us on IRC in
#icecast on Freenode.

Have a nice day!

-- 
Philipp.
 (Rah of PH2)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141228/94971ae3/attachment.sig>

From djjohnmcgrath at gmail.com  Sun Dec 28 14:55:35 2014
From: djjohnmcgrath at gmail.com (John Gmail)
Date: Sun, 28 Dec 2014 14:55:35 +0000
Subject: [Icecast] bored? Become a Icecast volunteer
In-Reply-To: <20141228112959.29B9B12CFE@grassland.keep-cool.org>
References: <20141228112959.29B9B12CFE@grassland.keep-cool.org>
Message-ID: <AEB51290-4C8F-4120-B82D-B2B0FE2DDE6C@gmail.com>

Hi Philip, 

I'm very interested in volunteering to help out the icecast project. I have limited programming skills, but am very enthusiastic to help this project.

Let me know what I can do!

John McGrath
07949709445

> On 28 Dec 2014, at 11:29, Philipp Schafft <lion at lion.leolix.org> wrote:
> 
> Good morning everyone!
> 
> As some of you may already have noticed we made quite some progress
> during the last few weeks. Icecast got some major updates to internal
> parts. Visible to the outside are the new tags <role> and <event>.
> 
> Those changes lead to need of updating documentation. Something we have
> been working on anyway. Beside documentation also testing is a topic
> getting more and more important to improve stability and performance.
> 
> As the current team can hardly handle all those in-time and that will
> delay releases, so we are looking for some volunteers.
> 
> There are many tasks to do. Also no programming skills required! There
> is something useful to do for _everyone_ who wants to help and any time
> amount you want to spend!
> 
> If you are interested just reply to this mail or join us on IRC in
> #icecast on Freenode.
> 
> Have a nice day!
> 
> -- 
> Philipp.
> (Rah of PH2)
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From thomas at ruecker.fi  Mon Dec 29 13:26:52 2014
From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=)
Date: Mon, 29 Dec 2014 13:26:52 +0000
Subject: [Icecast] Looking for company behind serverhostingcenter.com and
 directhostingcenter.com for causing problems on dir.xiph.org
Message-ID: <54A1569C.2090903@ruecker.fi>

Hi everyone,

as most of you probably know we are operating http://dir.xiph.org - an
open streaming directory.
There are always some misconfigured servers that keep trying to list
something broken. Most common are those where the server admin thinks
they can just put their homepage domain into the <hostname> field
(pro-tip: don't do that, ever, use the proper hostname of that machine!
Test the listenurl shown in admin!).

But there are also serial offenders, like *hostingcenter.com and their
many instances.
In most cases I manage to eventually reach someone or if it's just a
single instance, I blacklist it. Blacklisting actually has the positive
effect, that their error.log will contain a sensible error message, if
they bother to read it. Their listing was broken to begin with.
The problem with stream-hosting outfits is, that quite often they will
host a dozen or more servers on one IPv4 address and associated FQDN.
This means, that if I can't reach such a company, I am forced to pull
the plug on *ALL* their clients. I'm rather reluctant to do that, as it
will hit innocent bystanders who's only fault it is to have bought
services from an incompetent company.

So once again, if anyone has hints as to which company is hiding behind
the domains:
serverhostingcenter.com
directhostingcenter.com
and more importantly knows a way to reach someone responsible.

Just to be clear, I tried whois and mailed the address(es) there, I
tried to reach some of the customers of theirs, etc. I'm not willing to
invest more of my time into chasing them down anymore. Either I get a
direct technical contact at that company, or next week their domains and
IP ranges will be blacklisted from dir.xiph.org, collateral damage assumed.

If for some reason you don't want to post to the mailing list, then
*don't* press reply but send a mail to thomas at ruecker.fi instead.

Cheers

Thomas

PS: If you have an Icecast server that's listing on dir.xiph.org, please
make sure to put a working technical contact email address into the
<admin> field. We're actually using that to reach out to people who
manage to break their listings and such.



From maartensvo at live.nl  Mon Dec 29 13:43:18 2014
From: maartensvo at live.nl (Maarten S)
Date: Mon, 29 Dec 2014 13:43:18 +0000
Subject: [Icecast]
 =?utf-8?q?Looking_for_company_behind_serverhostingcente?=
 =?utf-8?q?r=2Ecom_and_directhostingcenter=2Ecom_for_causing_problems_on_d?=
 =?utf-8?q?ir=2Exiph=2Eorg?=
Message-ID: <DUB407-EAS224F6D666875368883FAB7DCA510@phx.gbl>

Hi Thomas, 


directhostingcenter.com:


Registrant Organization: Internet and Computer Services, LLC (LINK WhoIs)

Tim Wood = Owner - Internet and Computer Services, LLC (LINK LinkedIn)


Also: LINK, press WEBMASTER, mail address =   timwood at timwood.net



Perhaps this is the one you are looking for.


Best regards, Maarten





Van: Thomas B. R?cker
Verzonden: ?maandag? ?29? ?december? ?2014 ?14?:?27
Aan: Icecast streaming server user discussions





Hi everyone,

as most of you probably know we are operating http://dir.xiph.org - an
open streaming directory.
There are always some misconfigured servers that keep trying to list
something broken. Most common are those where the server admin thinks
they can just put their homepage domain into the <hostname> field
(pro-tip: don't do that, ever, use the proper hostname of that machine!
Test the listenurl shown in admin!).

But there are also serial offenders, like *hostingcenter.com and their
many instances.
In most cases I manage to eventually reach someone or if it's just a
single instance, I blacklist it. Blacklisting actually has the positive
effect, that their error.log will contain a sensible error message, if
they bother to read it. Their listing was broken to begin with.
The problem with stream-hosting outfits is, that quite often they will
host a dozen or more servers on one IPv4 address and associated FQDN.
This means, that if I can't reach such a company, I am forced to pull
the plug on *ALL* their clients. I'm rather reluctant to do that, as it
will hit innocent bystanders who's only fault it is to have bought
services from an incompetent company.

So once again, if anyone has hints as to which company is hiding behind
the domains:
serverhostingcenter.com
directhostingcenter.com
and more importantly knows a way to reach someone responsible.

Just to be clear, I tried whois and mailed the address(es) there, I
tried to reach some of the customers of theirs, etc. I'm not willing to
invest more of my time into chasing them down anymore. Either I get a
direct technical contact at that company, or next week their domains and
IP ranges will be blacklisted from dir.xiph.org, collateral damage assumed.

If for some reason you don't want to post to the mailing list, then
*don't* press reply but send a mail to thomas at ruecker.fi instead.

Cheers

Thomas

PS: If you have an Icecast server that's listing on dir.xiph.org, please
make sure to put a working technical contact email address into the
<admin> field. We're actually using that to reach out to people who
manage to break their listings and such.

_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141229/73eb660e/attachment.htm>

From geoff at QuiteLikely.com  Mon Dec 29 14:04:46 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Mon, 29 Dec 2014 16:04:46 +0200 (IST)
Subject: [Icecast] Looking for company behind serverhostingcenter.com
 and directhostingcenter.com for causing problems on dir.xiph.org
In-Reply-To: <54A1569C.2090903@ruecker.fi>
References: <54A1569C.2090903@ruecker.fi>
Message-ID: <alpine.DEB.2.02.1412291603460.3168@voldemort.home>

Hi,

Have you tried doing a whois on the *IP address* and contacting the 
hosting company (assuming it's not one of the above)?

Geoff.



From thomas at ruecker.fi  Mon Dec 29 14:25:51 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Mon, 29 Dec 2014 14:25:51 +0000
Subject: [Icecast] Looking for company behind serverhostingcenter.com
 and directhostingcenter.com for causing problems on dir.xiph.org
In-Reply-To: <alpine.DEB.2.02.1412291603460.3168@voldemort.home>
References: <54A1569C.2090903@ruecker.fi>
	<alpine.DEB.2.02.1412291603460.3168@voldemort.home>
Message-ID: <54A1646F.3070809@ruecker.fi>

On 12/29/2014 02:04 PM, Geoff Shang wrote:
> Have you tried doing a whois on the *IP address* and contacting the 
> hosting company (assuming it's not one of the above)?

The IP range I checked belonged to some big data center company. I don't
remember if I tried to reach them too, probably did.
I haven't heard back from any of those.

I've probably spent several days worth of work on tracking down various
problematic Icecast instances and don't feel like wasting more time on
sending emails to addresses like "public.whois.lookup.emaill.address@"
(actual local part on whois email!).

I sent this email to the list in the hope someone would actually know
the company.
I know how to use whois for networks and domains, but I'm not willing to
waste *more* time on that. The directory is a free service and it's my
time that goes into maintaining it and I'm not willing to pour more time
into finding some hoster who thinks playing hide and seek is cool. If
someone wants to pay me to play internet detective, contact me off list.

Cheers

Thomas



From geoff at QuiteLikely.com  Mon Dec 29 14:34:35 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Mon, 29 Dec 2014 16:34:35 +0200 (IST)
Subject: [Icecast] Looking for company behind serverhostingcenter.com
 and directhostingcenter.com for causing problems on dir.xiph.org
In-Reply-To: <54A1646F.3070809@ruecker.fi>
References: <54A1569C.2090903@ruecker.fi>
	<alpine.DEB.2.02.1412291603460.3168@voldemort.home>
	<54A1646F.3070809@ruecker.fi>
Message-ID: <alpine.DEB.2.02.1412291632560.3168@voldemort.home>

On Mon, 29 Dec 2014, "Thomas B. R?cker" wrote:

> I've probably spent several days worth of work on tracking down various
> problematic Icecast instances and don't feel like wasting more time on
> sending emails to addresses like "public.whois.lookup.emaill.address@"
> (actual local part on whois email!).

Fair enough!  If I were you, having made a good-faith effort to reach a 
human being with no luck, I'd pull the plug on them.   Either they will 
squeal, in which case you'll have found the human you've been looking for, 
or they won't care.

Geoff.

From hoggins at radiom.fr  Mon Dec 29 14:39:49 2014
From: hoggins at radiom.fr (Hoggins!)
Date: Mon, 29 Dec 2014 15:39:49 +0100
Subject: [Icecast] Looking for company behind serverhostingcenter.com
 and directhostingcenter.com for causing problems on dir.xiph.org
In-Reply-To: <54A1646F.3070809@ruecker.fi>
References: <54A1569C.2090903@ruecker.fi>	<alpine.DEB.2.02.1412291603460.3168@voldemort.home>
	<54A1646F.3070809@ruecker.fi>
Message-ID: <54A167B5.2090804@radiom.fr>

Hello Thomas,

Le 29/12/2014 15:25, "Thomas B. R?cker" a ?crit :
> The directory is a free service and it's my
> time that goes into maintaining it and I'm not willing to pour more time
> into finding some hoster who thinks playing hide and seek is cool.

This is slightly off-topic, but do you plan on hosting the directory on
volunteer mirrors as well ? (maybe you already do that).
We might have some spare bandwidth somewhere, maybe not enough, though.

    Hoggins!




From thomas at ruecker.fi  Mon Dec 29 14:44:39 2014
From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=)
Date: Mon, 29 Dec 2014 14:44:39 +0000
Subject: [Icecast] Looking for company behind serverhostingcenter.com
 and directhostingcenter.com for causing problems on dir.xiph.org
In-Reply-To: <DUB407-EAS224F6D666875368883FAB7DCA510@phx.gbl>
References: <DUB407-EAS224F6D666875368883FAB7DCA510@phx.gbl>
Message-ID: <54A168D7.9020001@ruecker.fi>

On 12/29/2014 01:43 PM, Maarten S wrote:
> Hi Thomas,
>
> directhostingcenter.com:
>
> Registrant Organization: Internet and Computer Services, LLC (LINK
> WhoIs <http://whois.icann.org/en/lookup?name=directhostingcenter.com>)

Yeah, I spent about half an hour trying to find more on that company,
but came up empty handed. Their name isn't really helpful when perusing
a search engine, even if you try forced grouping and other tricks.

> Tim Wood = Owner - Internet and Computer Services, LLC (LINK LinkedIn
> <https://www.linkedin.com/pub/tim-wood/85/3a3/1ba>)
> Also: LINK
> <http://mail.directhostingcenter.com/how-to-install-csf-and-lfd>,
> press WEBMASTER, mail address =   timwood at timwood.net
> <mailto:timwood at timwood.net>
>
> Perhaps this is the one you are looking for.
>

That looks like the best shot so far, thanks for finding that missing link.
I'll email that guy.
If anyone else has first hand knowledge, please let me know. You'd think
this outfit has some web page to advertize and sell their streaming
services.

Cheers

Thomas

> Best regards, Maarten
>
> *Van:* Thomas B. R?cker <mailto:thomas at ruecker.fi>
> *Verzonden:* ?maandag? ?29? ?december? ?2014 ?14?:?27
> *Aan:* Icecast streaming server user discussions <mailto:icecast at xiph.org>
>
> Hi everyone,
>
> as most of you probably know we are operating http://dir.xiph.org - an
> open streaming directory.
> There are always some misconfigured servers that keep trying to list
> something broken. Most common are those where the server admin thinks
> they can just put their homepage domain into the <hostname> field
> (pro-tip: don't do that, ever, use the proper hostname of that machine!
> Test the listenurl shown in admin!).
>
> But there are also serial offenders, like *hostingcenter.com and their
> many instances.
> In most cases I manage to eventually reach someone or if it's just a
> single instance, I blacklist it. Blacklisting actually has the positive
> effect, that their error.log will contain a sensible error message, if
> they bother to read it. Their listing was broken to begin with.
> The problem with stream-hosting outfits is, that quite often they will
> host a dozen or more servers on one IPv4 address and associated FQDN.
> This means, that if I can't reach such a company, I am forced to pull
> the plug on *ALL* their clients. I'm rather reluctant to do that, as it
> will hit innocent bystanders who's only fault it is to have bought
> services from an incompetent company.
>
> So once again, if anyone has hints as to which company is hiding behind
> the domains:
> serverhostingcenter.com
> directhostingcenter.com
> and more importantly knows a way to reach someone responsible.
>
> Just to be clear, I tried whois and mailed the address(es) there, I
> tried to reach some of the customers of theirs, etc. I'm not willing to
> invest more of my time into chasing them down anymore. Either I get a
> direct technical contact at that company, or next week their domains and
> IP ranges will be blacklisted from dir.xiph.org, collateral damage
> assumed.
>
> If for some reason you don't want to post to the mailing list, then
> *don't* press reply but send a mail to thomas at ruecker.fi instead.
>
> Cheers
>
> Thomas
>
> PS: If you have an Icecast server that's listing on dir.xiph.org, please
> make sure to put a working technical contact email address into the
> <admin> field. We're actually using that to reach out to people who
> manage to break their listings and such.
>
> _______________________________________________
> 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



From thomas at ruecker.fi  Mon Dec 29 14:57:02 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Mon, 29 Dec 2014 14:57:02 +0000
Subject: [Icecast] Looking for company behind serverhostingcenter.com
 and directhostingcenter.com for causing problems on dir.xiph.org
In-Reply-To: <54A167B5.2090804@radiom.fr>
References: <54A1569C.2090903@ruecker.fi>	<alpine.DEB.2.02.1412291603460.3168@voldemort.home>	<54A1646F.3070809@ruecker.fi>
	<54A167B5.2090804@radiom.fr>
Message-ID: <54A16BBE.6090107@ruecker.fi>

On 12/29/2014 02:39 PM, Hoggins! wrote:
> Hello Thomas,
>
> Le 29/12/2014 15:25, "Thomas B. R?cker" a ?crit :
>> The directory is a free service and it's my
>> time that goes into maintaining it and I'm not willing to pour more time
>> into finding some hoster who thinks playing hide and seek is cool.
> This is slightly off-topic, but do you plan on hosting the directory on
> volunteer mirrors as well ? (maybe you already do that).
> We might have some spare bandwidth somewhere, maybe not enough, though.

The directory runs quite well on Xiph.org hardware at OSUOSL at the moment.
Despite being bombarded with 50-100 yp listings and metadata updates per
second. I haven't looked at the bandwidth in a while, but serving yp.xml
(mostly the incompetent VLC implementation refusing to use compression)
cause about 5-10MBit/s egress 24/7

Despite being well designed and having served us quite well, the code
base has started to smell though and we're quite far into a rewrite.
For the curious http://dir-test.xiph.org/ (may be up or down at random
times)
The web interface styling will come last, so don't be discouraged by the
bare looks.

If someone wants to give the directory some load, feel free to add it to
your Icecast config. We could use some base load:
http://dir-test.xiph.org/cgi-bin/yp-cgi

Cheers

Thomas



From hoggins at radiom.fr  Mon Dec 29 15:03:41 2014
From: hoggins at radiom.fr (Hoggins!)
Date: Mon, 29 Dec 2014 16:03:41 +0100
Subject: [Icecast] Looking for company behind serverhostingcenter.com
 and directhostingcenter.com for causing problems on dir.xiph.org
In-Reply-To: <54A16BBE.6090107@ruecker.fi>
References: <54A1569C.2090903@ruecker.fi>	<alpine.DEB.2.02.1412291603460.3168@voldemort.home>	<54A1646F.3070809@ruecker.fi>	<54A167B5.2090804@radiom.fr>
	<54A16BBE.6090107@ruecker.fi>
Message-ID: <54A16D4D.8060600@radiom.fr>

Wow, that's cool !

Le 29/12/2014 15:57, "Thomas B. R?cker" a ?crit :
> The directory runs quite well on Xiph.org hardware at OSUOSL at the moment.
> Despite being bombarded with 50-100 yp listings and metadata updates per
> second. I haven't looked at the bandwidth in a while, but serving yp.xml
> (mostly the incompetent VLC implementation refusing to use compression)
> cause about 5-10MBit/s egress 24/7
>
> Despite being well designed and having served us quite well, the code
> base has started to smell though and we're quite far into a rewrite.
> For the curious http://dir-test.xiph.org/ (may be up or down at random
> times)
> The web interface styling will come last, so don't be discouraged by the
> bare looks.
>
> If someone wants to give the directory some load, feel free to add it to
> your Icecast config. We could use some base load:
> http://dir-test.xiph.org/cgi-bin/yp-cgi
>
> Cheers
>
> Thomas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141229/3c572717/attachment.htm>

From martin at jangowski-itservice.de  Mon Dec 29 14:46:58 2014
From: martin at jangowski-itservice.de (Martin Jangowski)
Date: Mon, 29 Dec 2014 15:46:58 +0100
Subject: [Icecast] Webradio directory
Message-ID: <54A16962.4040808@jangowski-itservice.de>

Hi guys,

I'm running "Radio Unicorns" for one year now, transmitting live 
coverage of one of Germanys best american football teams, the Schw?bisch 
Hall Unicorns. Technically, it's a root server running freebsd and the 
latest icecast. I had up to several hundred concurrent listeners this 
year and had the server tested up to 2000 listeners (had to tweak a few 
kernel parameters to achive that). The icecast server was our least 
problem, it just ran flawlessly.

One problem we're facing is how to propagate our service. The users 
looking at the team's website with a PC and a standard browser like 
Firefox, Chrome or IE just click on the link with the proper .m3u-File 
to listen to our radio, but the users with smartphones (iPhone & 
Android) have more problems. There are lots of apps out there that can 
listen to a .mp3-stream, but most of these apps don't show our server 
when searching for "Radio Unicorns". I listed our radio on xiph.org, but 
there have to be more public directories, because no app I checked finds 
Radio Unicorns when searching for it. There are lots of small radio 
stations listed in these apps, but I wasn't able to find out where these 
apps are looking for station listings and how to add our station to it.

If anyone out there could point me to these services, I'd be grateful. 
Thanks in advance!

Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141229/e7188320/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: martin.vcf
Type: text/x-vcard
Size: 319 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141229/e7188320/attachment.vcf>

From djjohnmcgrath at gmail.com  Mon Dec 29 15:18:48 2014
From: djjohnmcgrath at gmail.com (John Gmail)
Date: Mon, 29 Dec 2014 15:18:48 +0000
Subject: [Icecast] Webradio directory
In-Reply-To: <54A16962.4040808@jangowski-itservice.de>
References: <54A16962.4040808@jangowski-itservice.de>
Message-ID: <53624C77-6EF9-43D0-B93D-8BAC64E9244D@gmail.com>

Hi Martin, 

I use a muses which runs on all devices. The JavaScript is hosted by muses but it can be self hosted. I found that this was both the easiest and most cross platform solution. The player is here: www.zaumfm.com 

I'm not sure about where to get your station featured but will keep an eye on this thread for hints

John McGrath


> On 29 Dec 2014, at 14:46, Martin Jangowski <martin at jangowski-itservice.de> wrote:
> 
> Hi guys,
> 
> I'm running "Radio Unicorns" for one year now, transmitting live coverage of one of Germanys best american football teams, the Schw?bisch Hall Unicorns. Technically, it's a root server running freebsd and the latest icecast. I had up to several hundred concurrent listeners this year and had the server tested up to 2000 listeners (had to tweak a few kernel parameters to achive that). The icecast server was our least problem, it just ran flawlessly.
> 
> One problem we're facing is how to propagate our service. The users looking at the team's website with a PC and a standard browser like Firefox, Chrome or IE just click on the link with the proper .m3u-File to listen to our radio, but the users with       smartphones (iPhone & Android) have more problems. There are lots of apps out there that can listen to a .mp3-stream, but most of these apps don't show our server when searching for "Radio Unicorns". I listed our radio on xiph.org, but there have to be more public directories, because no app I checked finds Radio Unicorns when searching for it. There are lots of small radio stations listed in these apps, but I wasn't able to find out where these apps are looking for station listings and how to add our station to it.
> 
> If anyone out there could point me to these services, I'd be grateful. Thanks in advance!
> 
> Martin
> <martin.vcf>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141229/64f6ad89/attachment.htm>

From hoggins at radiom.fr  Mon Dec 29 16:59:03 2014
From: hoggins at radiom.fr (Hoggins!)
Date: Mon, 29 Dec 2014 17:59:03 +0100
Subject: [Icecast] Directory listing details (was : Looking for company
 behind serverhostingcenter.com and directhostingcenter.com for causing
 problems on dir.xiph.org)
In-Reply-To: <54A16BBE.6090107@ruecker.fi>
References: <54A1569C.2090903@ruecker.fi>	<alpine.DEB.2.02.1412291603460.3168@voldemort.home>	<54A1646F.3070809@ruecker.fi>	<54A167B5.2090804@radiom.fr>
	<54A16BBE.6090107@ruecker.fi>
Message-ID: <54A18857.30303@radiom.fr>

Hello Thomas,


Le 29/12/2014 15:57, "Thomas B. R?cker" a ?crit :
> Despite being well designed and having served us quite well, the code
> base has started to smell though and we're quite far into a rewrite.
> For the curious http://dir-test.xiph.org/ (may be up or down at random
> times)
> The web interface styling will come last, so don't be discouraged by the
> bare looks.
>
> If someone wants to give the directory some load, feel free to add it to
> your Icecast config. We could use some base load:
> http://dir-test.xiph.org/cgi-bin/yp-cgi

We started pushing data to this test directory as well. Can you tell me
how we should format our genres list if we have several ? It appears
slight differently between the current and the new one, but maybe it's
simply because it's still beta.

Thanks !


From erm13martinez at gmail.com  Tue Dec 30 06:40:40 2014
From: erm13martinez at gmail.com (Eduardo Martinez)
Date: Mon, 29 Dec 2014 22:40:40 -0800
Subject: [Icecast] bored? Become a Icecast volunteer
In-Reply-To: <20141228112959.29B9B12CFE@grassland.keep-cool.org>
References: <20141228112959.29B9B12CFE@grassland.keep-cool.org>
Message-ID: <CAJ8tkjg9chtjwRBQn_pp37CmdLwhLqLrkRaX3QSYJRuSS6JwJQ@mail.gmail.com>

Hello Philipp,

Please let me know how I can help.
 On Dec 28, 2014 3:30 AM, "Philipp Schafft" <lion at lion.leolix.org> wrote:

> Good morning everyone!
>
> As some of you may already have noticed we made quite some progress
> during the last few weeks. Icecast got some major updates to internal
> parts. Visible to the outside are the new tags <role> and <event>.
>
> Those changes lead to need of updating documentation. Something we have
> been working on anyway. Beside documentation also testing is a topic
> getting more and more important to improve stability and performance.
>
> As the current team can hardly handle all those in-time and that will
> delay releases, so we are looking for some volunteers.
>
> There are many tasks to do. Also no programming skills required! There
> is something useful to do for _everyone_ who wants to help and any time
> amount you want to spend!
>
> If you are interested just reply to this mail or join us on IRC in
> #icecast on Freenode.
>
> Have a nice day!
>
> --
> Philipp.
>  (Rah of PH2)
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141229/84c1ae34/attachment.htm>

From thomas at ruecker.fi  Wed Dec 31 20:45:26 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Wed, 31 Dec 2014 20:45:26 +0000
Subject: [Icecast] [Icecast-dev] Icecast 2.5 beta1 release
Message-ID: <54A46066.4070206@ruecker.fi>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is to announce the release of Icecast 2.5 beta1 (aka 2.4.99.1).

We've worked on some important features over the last months and we're
looking forward to testing and feedback.
(Please do NOT cross-post to both lists, do NOT reply to the Icecast
mailing list, PLEASE reply to icecast-dev at xiph.org only).

 * <role> replaces old style <authentication> items
 * <event> triggers
 * <resource> replaces <alias> and offers more functionality
 * additional stream metadata exposed
 * additional stats XML output (e.g. listeners, used by e.g. licensing
   services, may need ?omode=legacy)

Most of the documentation still needs to be written, but you'll find
quite some hints in the ChangeLog. We'll try to update the online
documentation as it improves, so it might be good to check:
http://icecast.org/docs/icecast-trunk/ - as the included docs will be
outdated. If you have questions, ask them on the developer mailing
list or on IRC.

Please test this and also all other new 2.5 features and report to the
dev mailing list with your observations and findings.
We've spent considerable time looking for memory leaks using Valgrind,
but there probably still are some bugs and leaks.
http://trac.xiph.org has a version option of "2.5-beta1" please use
that when filing tickets.

Source tar ball:
http://downloads.xiph.org/releases/icecast/icecast-2.5-beta1.tar.gz
sha256sum:
df5061593f61a258d92381924981dae4d5ad09296b5ff5708d94c4685fe41fa7
md5sum:
9155b5a710ffe4ed8da1c3f7eefe8578

Windows build:
[not uploaded yet, but will appear soon? as]
http://downloads.xiph.org/releases/icecast/icecast_win32_2.5-beta1.exe

I'll also see to get a testing repository up on OBS with packages, just
as we have for the latest stable release.

We expect to make at least two more beta releases over the next few
months before we will release a stable Icecast 2.5.0

2.5 beta1 is not intended for production use, so if it scares your cat,
bites your dog and proceeds to blow up - enjoy the fireworks.

Coincidentally - Happy New Year!

Cheers

Thomas

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlSkYGUACgkQfkVKO9VkYGk53gCeKxlJt9jA7WBoDqcfztRGhEpv
RGQAnj4MFZ7aSXiYGCkJ8g73IPpba32a
=yb5p
-----END PGP SIGNATURE-----