From owner-freebsd-questions Sun Dec 5 0:55:18 1999 Delivered-To: freebsd-questions@freebsd.org Received: from ns1.websitefactory.net (ns1.websitefactory.net [208.26.83.130]) by hub.freebsd.org (Postfix) with ESMTP id AA4E2150F2 for ; Sun, 5 Dec 1999 00:55:10 -0800 (PST) (envelope-from jweaver@websitefactory.net) Received: from asbestos.websitefactory.net (asbestos.websitefactory.net [208.26.78.16]) by ns1.websitefactory.net (Postfix) with ESMTP id 1B9CFAE64A; Sun, 5 Dec 1999 03:54:33 -0500 (EST) Date: Sat, 04 Dec 1999 15:52:51 -0500 From: Jonathan Weaver To: Carl Johan Madestrand , freebsd-questions@freebsd.org Subject: Re: XMMS problem Message-ID: <3724933406.944322771@asbestos.websitefactory.net> In-Reply-To: <19991204133243.D377@norrgarden1.norrgarden.se> X-Mailer: Mulberry (Win32) [2.0.0b4, s/n U-301192] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --On Saturday, December 04, 1999 1:32 PM +0100 Carl Johan Madestrand wrote: > Hi > > My /var/log/messages always fill up with kernel error messages while > running XMMS: > > Dec 3 23:15:11 norrgarden1 /kernel: cmd xmms pid 84671 tried to use > non-present sched_getscheduler > Dec 3 23:24:46 norrgarden1 last message repeated 2 times > > > Any clue as to whats going on? > > Thanks > Yes, you need to enable the POSIX realtime extensions in your kernel. (Recompile) XMMS should work without any major problems then, short of the really bad ShoutCast/IceCast support. (Eats 100% CPU, versus 5% in Windows/Winamp) - Jonathan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message