Date: Tue, 25 Mar 2003 07:51:47 -0800 (PST) From: Robert Watson <rwatson@FreeBSD.org> To: archie@precisionio.com, rwatson@FreeBSD.org, freebsd-bugs@FreeBSD.org, rwatson@FreeBSD.org Subject: Re: bin/50260: can't get my own policy from sched_getscheduler() Message-ID: <200303251551.h2PFpln9046875@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
Synopsis: can't get my own policy from sched_getscheduler() State-Changed-From-To: open->closed State-Changed-By: rwatson State-Changed-When: Tue Mar 25 07:47:49 PST 2003 State-Changed-Why: In FreeBSD 5.0, the POSIX4 (1003.1b) scheduler interfaces are fully accessible to user applications by virtue of re-working the inter-process access control as part of the TrustedBSD work. I just committed changes to FreeBSD 4.8 and -STABLE to permit the use of sched_getparam() and sched_getscheduler() for non-root processes, as well as fixed serious bugs that caused the return value to be returned in the wrong process. This appears to be sufficient to get applications such as the JDK up and running, although it doesn't completely open up the enhanced scheduler interface as backporting the complete inter-process access control rewrite is probably not worth the time investment at this point. If this doesn't resolve the problems you're experiencing, please let me know. Responsible-Changed-From-To: freebsd-bugs->rwatson Responsible-Changed-By: rwatson Responsible-Changed-When: Tue Mar 25 07:47:49 PST 2003 Responsible-Changed-Why: I've committed a fix; will take responsibility for any follow-ups. http://www.freebsd.org/cgi/query-pr.cgi?pr=50260 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303251551.h2PFpln9046875>