search for: 007364

...l - http://dovecot.org/list/dovecot-cvs/2007-January/007393.html Corrupted view errors: - http://dovecot.org/list/dovecot-cvs/2007-January/007366.html - http://dovecot.org/list/dovecot-cvs/2007-January/007368.html Corrupted cache file errors: - http://dovecot.org/list/dovecot-cvs/2007-January/007364.html Fixed a lot of crashes whenever something went wrong (I deleted index files every 3 seconds until it crashed, last run went for several minutes before I stopped trying): - http://dovecot.org/list/dovecot-cvs/2007-January/007397.html -------------- next part -------------- A non-text attachm...

...ISHED connection is the instance which didn't get blocked by > iptables. > and those sockets seem to remain in CLOSE_WAIT until i kill the ices > process. This sounds similar to what I encountered when I first set up ices2 -- see <http://lists.xiph.org/pipermail/icecast/2004-July/007364.html>. In short, if you're streaming over a WAN, the main ices2 branch is woefully inadequate, and you ought to try Karl Heyes' branch at <http://mediacast1.com/~karl/>, as he described in his reply to my original email. (Don't get ices 2.0.1, which is merely a point release...

hi everyone, congratulations on the release of icecast 2.1.0 I presume this is the right place to post about iceS. please correct if wrong. I have a two instance setup, and have been finding that after a network error occurs, the instance does not reconnect. The source server is behind a linux NAT box. I have simulated the problem by using iptables REJECT with tcp-reset and here is the