similar to: Crash in Icecast-2.3.1 (in source_recheck_mounts)

Hi all, I'm experiencing a crash in Icecast 2.3.1 when a lot of sources (300) are disconnecting at more-or-less the same time. I run a test where I set Icecast configured with 300 mount points on one machine and attach 300 ezstream source clients from another machine serving a low-bitrate stream (24 kbit/sec). When I 'killall ezstream' to stop all sources at the same time Icecast

aight than thanks Geoff i'll just use version 2.2 for right now.. thanks for the update (u might say) 73's and 88's DE TODD KC?CCB DN84FK ICQ #: 71473037 MYSPACE : http://www.myspace.com/kc0ccb NET: http://www.webspawner.com/users/hamradio/index.html TEMP WEB SERVER: http://209.159.208.18:8000/stream.m3u ----- Original Message ----- From: <icecast-request@xiph.org> To:

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,

hey everybody, just wanted to know if there's anything i need to do different to install and confiqure version 2.3.1 as oposed to version 2.2 or not ?? and what exactly is there in 2.3.1 anyways ?? is it any better then version 2.2 ?? and is there any way i can edit the server to make my scanner go live (like right the the second) PS: in the mean time i will

Is there a mechanism or technique to allow me to boost document relevancy, independent of search terms? I do not necessarily want to do any of the sorts described here: http://xapian.org/docs/sorting.html#sorting-by-value. Rather I'd like to sort by something like relevancy*boost factor, like: http://lucene.apache.org/java/2_3_2/api/org/apache/lucene/document/Document.html#setBoost(float)