similar to: No subject

Hi I've got everything running OK but now have a couple of questions: I'm occasionally getting "504 server full" errors at the client and in the icecast access log. Is this caused by me exceeding the value set in the <max-listeners> section of icecast.xml for each mount point? Also, when I HUP ices it fails to properly reload the Perl module... ices catches the

Hi All-- I'm trying to get icecast working with ices, but I'm having a problem with the PQueue module. I'm including my ices.connf file and verbose output when running in non-daemon mode below. I'm running on Fedora Core 1, and have all packages updated (via yum). I'd greatly appreciate any insights. Jim <p><?xml version="1.0"?>

Hiya I'm completely stumped on reloading the playlist... If I send ices a SIGHUP signal it appears to reload the Perl module but not execute any code. The messages I'm getting are: DEBUG: Caught SIGHUP, cycling logfiles and reloading playlist... DEBUG: Interpreting [ices_shutdown] DEBUG: perl [ices_shutdown] returned 1 values, last [1] DEBUG: Done interpreting [ices_shutdown] DEBUG:

We have installed IceCast2 and Ices0.3 and it works very well - with builtin playlist! When I write my own playlist handler - similar to the preconfigured ices.pm.dist - I get a perl_parse() error while starting ices. So ices exits. --- Code: --- # At least ices_get_next must be defined. And, like all perl modules, it # must return 1 at the end. # Function called to get the next filename to

At 1:48 PM -0400 7/6/01, Brendan Cully wrote: >On Friday, 06 July 2001 at 10:32, tom erbe wrote: >> icecast 1.3.10 is the server i'm running, but its ices 0.1 that gives >> me a segfault under solaris. it works just fine on my linux box. ices > >The segfaults are a stack size problem. Try changing STACKSIZE near >the top of thread/thread.c from 8192 to 65536 or so...

Brendan Cully wrote: > > The format of ices.conf changed somewhat in 0.2, to support multiple streams > from the same playlist with different reencoding options. In short, these > settings have been moved into the Stream node. For more info have a look > at the sample ices.conf included with the distribution. I did modify my ices.conf when I made the upgrade. Here's my

On Thu, 17 Feb 2005 09:40:09 -0800, Brendan Cully <brendan@xiph.org> wrote: > On Thursday, 17 February 2005 at 12:20, Dan Stowell wrote: > > So will ices0 - that's what I use, and I nudge it along all the time. > > There is one significant problem with ices0 which is that if you nudge > > it while it's playing *the very last* entry in a playlist, it seems to >

On Wednesday, 06 June 2001 at 18:59, Jack Moffitt wrote: > > Do icecast/ices 2 ONLY support vorbis, or can they still handle mp3s? > > I am not ready to stream only vorbis yet, since I don't know how many > > people are equipped to hear them. If icecast/ices 2 don't support mp3, > > then I have some hacking to do on ices 1 (namely, I want to play the > > same

OK...messing with 'gdb' (of which I am completely new to) <p>Here's is the complete output from what I've done with 'gdb' ---------------------------------------------------------------- # gdb ices GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it

At 4:37 PM -0400 7/6/01, Brendan Cully wrote: >On Friday, 06 July 2001 at 13:21, tom erbe wrote: >> At 1:48 PM -0400 7/6/01, Brendan Cully wrote: >> > > 0.2 doesn't segfault, but it seems to overrun the server (if that >> >> makes any sense), it plays a 3 minute file in seconds. >> > >> >I'd like to know more about this. Are you

On Wednesday, 01 August 2001 at 15:12, Robin P. Blanchard wrote: > > > > Ices will reload the playlist file if it changes on disk. So if the > > > file changes every track, everything will be fine. Alternatively you > > > could write your MP3 to a FIFO, which ices could pipe to your icecast > > > server. > > > > that looks like an interesting

Thanks for the suggestion. It turns out that debug for ices told me nothing but debug for icecast 2.2.0 showed that it was terminating the source at the same place in the playlist, apparently due to a lack of trailing metadata in one particular file -- icecast saw it as end of stream. After checking code updates on the TRAC system, I installed the kh branch of icecast (kh13) and this seems

hello all: i have icecast2 and ices2 built and working great, streaming ogg like it aint no thing...i have a bunch of (legacy) mp3's however, that id like to stream to the icecast2 server, which means ices-0.2.3 (i know i could just convert all the old mp3s to ogg, but thats not being very nice to people with windows media player, for example...). i have an old ices (i think its from a

Hi, I'm looking into switching from liveice to ices. I like to provide the same stream at two bitrates (56/24), which is simple from liveice. But my initial impression is that you can't do this within ices? Do you need to run two separate instances of ices with different configurations? I'd like to run only one because: 1. only one mp3 decoder runs (saves CPU on my K6-3/450) 2. the

On Sunday, 24 June 2001 at 22:24, Jack Moffitt wrote: > > I decided to make a few shell scripts that can be used to connect to > > icecast, decode/reencode a stream, and then send the result back to icecast. > > > > I guess this can be done with liveice, but this seemed like a simpler > > solution for my needs. I have it triggered by a cgi script that i click

Brendan Cully wrote: >>kill -SIGHUP <icespid> >>But this don't work! :( > > That should work. Hmm ... How can I recognize, that the changes are detected? I Changed the playlist, sent the kill -SIGHUP command, and watched the cue File. But nothing changed. Or ... did ices finished playing the current song and starts after that the new song from the new playlist?

From: "Brendan Cully" <brendan@icecast.org> > On Tuesday, 10 July 2001 at 14:10, Nick Ludlam wrote: > > From: "Brendan Cully" <brendan@icecast.org> > > > On Tuesday, 10 July 2001 at 03:21, Nick Ludlam wrote: > > > > From: "Brendan Cully" <brendan@icecast.org> > > > > > That handles the segfault, I

Great. If you have some pointers with further explanations, that'd be great, because lately I've been wondering why 256 MB fills up all the way to the point my desktop system slows to a crawl. Someone seriously messed with the 2.4.x memory handling. It's probably caching and mmap'ing lots of stuff but I want it to pipe DOWN ! o any pointers are appreciated. Especially on the

i'd also point out that memory "use" under linux can be deceptive. -----Original Message----- From: owner-icecast@xiph.org [mailto:owner-icecast@xiph.org]On Behalf Of Brendan Cully Sent: Monday, September 10, 2001 4:00 PM To: icecast@xiph.org Subject: Re: [icecast] Ices memory leak? On Monday, 10 September 2001 at 12:45, Jason Mansfield wrote: > Is anyone else experiencing what

On Wednesday, 01 August 2001 at 14:37, Robin P. Blanchard wrote: > you may or may not be acquainted with the program otto; it is > a web-based jukebox solution. it has the ability to play both > locally as well as to an icecast server via ices. however, as > there is not a static playlist, ices needs to to exit after > streaming an individual song. the author of otto had the