search for: bkyoung

...ing Fedora systemd support. A basic start may be as listed below. Just note that after install, depending on the instance of ices0 being started, use 'systemctl start ices0 at 0.service'. See the installed unit service file ices0 at .service for additional information. Spec file: ftp://ftp.bkyoung.com/pub/specs/ices0.spec.tgz Maybe to save exporting the sources, here is the source tarball ftp://ftp.bkyoung.com/pub/specs/ices0-0.4.svn18725.tar.gz

Hello! I started the IceCast using Valgrind, just like you suggested before. It started with ~37MB of residend memory used by the Valgrind process and then started to grow steadily after the IceS stream start. I waited till the memory used by Valgrind reached ~79MB and stopped the IceS stream. The Valgrind memory usage also stopped to grow. I waited for several hours and checked the memory

Hi - I'm using Icecast to stream some audio that I embed in an <audio> tag on a webpage. This is working great for desktop browsers and on iOS, but it doesn't work on Android. It looks like Chrome mobile sends the header "Range: bytes=0-1" and then doesn't try to load any more data when Icecast responds with a 0 byte "HTTP/1.0 200 OK" response. From my

The following patch attempts to make the source client user agent and the max listener client connection duration information available to (icecast 2.3.2) xsl stylesheets. Will there be any memory leak issues in the lower level functions like the acl, etc. when the source is disconnected, when servicing queries, or otherwise? BEGIN icecast-2.3.2-moremntinfo.patch diff --git src/source.c

Doesn't the missing "Accept-Ranges" in response inform the client to resend the request without Range:? I think only the file server would serve partial content in this way, as the streaming server implies partial content as part of its protocol. Anyway, the response seems as requested. 0 (empty) or 1 bytes partial content was requested, and empty response returned. On Wed,

Hi All, I am in the process of trying to build a Samba server to replace our aging EMC Celerra file server appliance.? The goal, ultimately, is to build a file server on which we can migrate a file share from the Celerra (ACL permissions and all) over to Samba, where the file share can be exported via NFS as well as Samba, AND the permissions we see in Linux are what we see in Windows (as well as