similar to: Icecast dropping streams

> These are usually down to non-utf8 chars being sent to icecast. Check > the metadata being sent That's quite likely, since some of the tracks have cyrillic ID3 tags. What should I do to cirvumvent that? > That message occurs if icecast hasn't received any data after a certain > amount of idle time (<source-timeout> seconds). This could be down to > the source

Hi, I need to compile Icecast on a kind of ancient AIX machine. I compiled all the required libraries, except libvorbis, and I can't make it compile at all. Is there a way to compile Icecast without Ogg Vorbis support? Thanks! -- Regards, Alek Andreev alek@zvuk.net

On Mon, 2005-02-07 at 14:05, Alek Andreev wrote: > Hi, > > I had my stream running from ezstream 0.1.2 to icecast 2.2.0. It's been > going for about a week, but two days ago I changed my icecast.xml. Since > then, Icecast dropped my sources and stopped transmission twice. > Everytime, it spew out > > xmlEncodeEntitiesReentrant : char out of range These are usually

In R's maptools package, is there a built-in function to test if a given point is "inside" a given polygon on the map? The map was loaded from an ESRI Shapefile. The point's latitude and longitude are known. Thank you! Aleks -- ------------------------ Aleksandr Andreev Fulbright Fellow Graduate School of Management St Petersburg State University

Greetings! I am trying plot some data on a map in R. Here's the scenario. I have a variable called probworkinghealthy which contains a predicted probability of employment for every individual in my sample (about 100,000 observations). I have another variable, called a001ter, which contains the subject of residency in the Russian Federation (akin to a US state) for every individual in the

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

Hi, I've been noticing a huge memory usage on Icecast 2.3.2 on multiple debian instances. They are using like 100 MB after a day and going on until they hit like 1 GB.. So I ran one in valgrind, and killed it after ~24h, here is the output: ==30481== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 38 from 3) ==30481== malloc/free: in use at exit: 44,448,584 bytes in 44,470 blocks.

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

A few years back, I wrote some code to plot maps with the maptools package. Now I am trying to reproduce my results, only to find out that maptools has been updated and my code no longer works. I've been able to fix the first part of it by forcing spb <- maptools:::read.shape("/home/sasha/Documents/maps/spb.shp") (as read.shape has been deprecated) but now when I do plot(spb,

Hi David, On 28.10.2011 13:05, David Chisnall wrote: > I disagree there. Perl is pretty much guaranteed to be installed on any UNIXish system. Even FreeBSD, which has removed it from the base system, tends to install the Perl package by default. In contrast, a lot of the machines I use don't have Python installed. I need to install it if I'm doing LLVM development because it's

Alek Paunov <alex at declera.com> writes: >> That said, if the information required for the build is going to be >> made explicit, maybe this isn't such a problem, as other tools can be >> written to parse it and run the build. > > Absolutely - once the generators are prototyped and tested in Python, if > current Perl (presence) > Python's, they can be

Greetings. I'm trying to label some points using the identify() command. The labels and the coordinates are coming from a csv file. The file encoding is UTF-8. If I use labels in Latin characters, everything comes out OK. But when I switch to using labels in Cyrillic, I get garbage. To check that my file is not corrupt, I've attempted to create the labels using the text() command and

Hi Jeroen, I just realised that the version I use is very old -- 4.1. So first what I should do -- updating it and only then come here , asking for clarification. ??, 27 ????. 2024??. ? 14:19, Jeroen Koekkoek <jeroen at nlnetlabs.nl>: > Hi Peter, > > NSD processes updates in batches. xfrd receives the [AI]XFR and > schedules a reload for the main process, which in turn forks

Short question: is there way to tell EM to actually send data after send_data call? I''m building a file transferring app. I send Mashal.dump''ed metadata first, and then - the file contents (chunked). I found a silly bug: receive_data() gets marshalled metadata and the first chunk of the file in a single variable. Like that: c1.send_data("meta")

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

Hi Peter, NSD processes updates in batches. xfrd receives the [AI]XFR and schedules a reload for the main process, which in turn forks new serve children. The served-serial is updated after main reports success, the commit-serial (update written to disk) is updated before the reload (to explain the serials). The difference in timestamp can be explained by the fact that NSD looks up if the serial

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

Greetings! I attempted to read a STATA 10 file using the following syntax: library(foreign) data <- read.dta("~/Documents/agestandard/analysis.dta") I got the following error: *** stack smashing detected ***: /usr/lib/R/bin/exec/R terminated ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7c13138]

hi has anyone seen this error before: [root@machine root]# error : xmlEncodeEntitiesReentrant : input not UTF-8 unfortunately i cannot see what application is causing this error but i suspect that it is icecast because of the XML config file and we have made some changes recently. i have issued thess commands to try to get something from the logs: [root@machine root]# grep -r -i

Hi, the reporting person has tried also with vanilla icecast source compiled. The setup is: Liquidsoap in MP3 mode sending a stream Winamp pulling the stream A flash applet requesting a custom XSLT file every 10s The output of valgrind is: ==13821== ==13821== HEAP SUMMARY: ==13821== in use at exit: 1,744,928 bytes in 4,194 blocks ==13821== total heap usage: 41,508 allocs, 37,314 frees,