Date: Fri, 17 Mar 2006 19:03:19 +0100 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= <gabor.kovesdan@t-hosting.hu> To: Frank Steinborn <frank@ircnow.org> Cc: freebsd-questions@freebsd.org Subject: Re: Problem with shoutcast port Message-ID: <441AF9E7.3040304@t-hosting.hu> In-Reply-To: <20060317174957.GA9927@scott.blazing.de> References: <8dc358df0603141008y65a40e37m86b004362ce3f4b5@mail.gmail.com> <20060317172640.GA3734@scott.blazing.de> <441AF4A9.6090802@t-hosting.hu> <20060317174957.GA9927@scott.blazing.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Frank Steinborn wrote: >Kövesdán Gábor wrote: > > >>I'm the maintainer of the shoutcast port. As you probably know, it's a binary >>port, since shoutcast is a closed-source application, so the port do just some >>simple tasks: patching config file, creating a user for shoutcast and >>installing the binary and the rcNG script. I think, the problem is with the >>binary, not with the port, so I can't fix it. Signal 11 means segmentation >>violation. Anyway, can you try to install it manually and check if it runs, >>please? All you have to do is to download from the shoutcast website, extract >>and run with the default configuration. >>If it fails, too, you might want to report it to the shoutcast team. If it >>works, please write back to me, attach your config file and include the output >> >> >It *is* a problem in the FreeBSD-binary from Shoutcast. That's why I >told the OP to use the Linux-version of Shoutcast. Probably someone >should do a linux-shoutcast port :-) > >Frank > > Or submit a bugreport to the developers of shoutcast. I'd do that but I hasn't been able to reproduce the error so far. Gabor Kovesdan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?441AF9E7.3040304>