On 25-Feb-2003 Bob Bishop wrote: > At 14:56 25/2/03, Murray Stokely wrote: >>This has been a problem for years and it affects other Linux >>appications such as LabView. There is some commented out code in >>linux_sched_getscheduler() function that provides the proper >>functionality. It's unclear to me why the code was commented out in >>the first place, but it would be really nice to get that resolved once >>and for all. > > According to kern/40611, the problem is in posix4/p1003_1b.c not in the > linux wrapper. The updated patch in the PR audit trail seems to work.
There is a much simpler patch one can do: Index: p1003_1b.c =================================================================== RCS file: /usr/cvs/src/sys/posix4/p1003_1b.c,v retrieving revision 1.5.2.1 diff -u -r1.5.2.1 p1003_1b.c --- p1003_1b.c 3 Aug 2000 01:09:59 -0000 1.5.2.1 +++ p1003_1b.c 25 Feb 2003 16:17:55 -0000 @@ -62,7 +62,7 @@ * only root can do this. */ -#if 0 +#if 1 /* * This is stolen from CANSIGNAL in kern_sig: * Basically, it changes p31b_proc() to not always return an error for non-root. If rwaston@ signs off on the security implications (should be minimal, basically means that you can change your own scheduling params and can change the params of other processes you own) then I would prefer this patch. I don't know why the check was turned off. The entire #if 0 / #else / #endif seems to have been around since revision 1.1. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
