search for: imares

Hiya Karl (and everybody else), I noticed today that ices 2.0-kh60a came out last January, and opted to give it a try. Unfortunately, it just wouldn't work at all, so I had to back down to 2.0-kh60. What I get in my log is this: [2006-04-21 21:16:18] DBUG om_shout/check_shout_connected Time we started stream on ice.imars.net:8000/cigr.ogg [2006-04-21 21:16:19] EROR

Hi everybody, I'm in charge of an ices2 setup that's broadcasting a local radio station on the Net, and I'm currently under fire because one of our streams has been down twice in two days, forcing me to restart ices2 on each occasion. Our client is understandably unhappy about this. OUR SETUP: I've got ices2 installed on a local machine, broadcasting to an icecast server across

Fr?d?ric Bri?re wrote: > Hiya Karl (and everybody else), hi > I noticed today that ices 2.0-kh60a came out last January, and opted to > give it a try. Unfortunately, it just wouldn't work at all, so I had to > back down to 2.0-kh60. ok, send me your xml, so I know what parts are being used, I have to check the code for something else, but it does look to be the libshout part

...However, I'm at a loss on how to maintain the exact RGB-information of each pixel using the 'image' function. Any suggestions on this issue would be most welcome. Thanks in advance! Cheers, Pepijn de Vries M.Sc. Research Scientist Institute for Marine Resources and Ecosystem Studies (IMARES) www.imares.nl

Package: logcheck Version: 1.2.39 Severity: normal Since I've upgraded my servers to sarge, I'm getting mail every hour for stuff that was duly included in /etc/logcheck/logcheck.ignore. Turns out that sarge's version no longer reads that file. If this was a conscious decision, then there should be some warning about this when upgrading (via debconf of NEWS.Debian). Also, the