Does anyone have any experience with this system call?
I'm trying to set to the FIFO scheduler policy (for a short time of
course), and get an Operation not permitted error back - in spite of
having the image SETUID and running it as root (a bit redundant - but
I'm grasping at straws now).
Bruce Dawson j...@codemeta.com writes:
Does anyone have any experience with this system call?
I'm trying to set to the FIFO scheduler policy (for a short time of course),
and get an Operation not permitted error back - in spite of having the image
SETUID and running it as root (a bit
Bruce Dawson writes:
Does anyone have any experience with this system call?
Can you give us some code with your exact setup for
sched_setscheduler()?
Using this call requires a bit of setup ; there are a quite a few
things that could go wrong or not be setup correctly, etc. Being able
to
On Thu, Nov 8, 2012 at 2:17 PM, Kevin D. Clark kevin_d_cl...@comcast.netwrote:
Bruce Dawson writes:
Does anyone have any experience with this system call?
Can you give us some code with your exact setup for
sched_setscheduler()?
As a secondary note, the permitted message you are
The (rather severely hacked) code is attached - I'm using a netbook with
cygwin right now and can't seem to do a cutpaste from the window.
It was built with cc latencytest.c -o latencytest
The executable was SetUID and owned by root. I also tried sudo'ing it.
Output:
jbd@beaglebone:~$
Strange. I made a few minor changes (see attached patch)
and when I run your code on my test machine running Linux kernel
2.6.35 I get the following output:
$ sudo ./latencytest
./latencytest starting...
My original scheduling policy is SCHED_OTHER (0)
The original minimum scheduling
On 2.6.31-11-rt (Ubuntu 10.04 realtime kernel)
./a.out starting...
My original scheduling policy is SCHED_OTHER (0)
The original minimum scheduling priority is 0, the maximum is 0
sched_get_priority_max(1) returned 99
sched_get_priority_min(1) returned 1
My target scheduling policy is
On Thu, Nov 8, 2012 at 5:54 PM, Thomas Charron twaf...@gmail.com wrote:
On 2.6.31-11-rt (Ubuntu 10.04 realtime kernel)
./a.out starting...
My original scheduling policy is SCHED_OTHER (0)
The original minimum scheduling priority is 0, the maximum is 0
sched_get_priority_max(1) returned
On 11/8/2012 6:56 PM, Thomas Charron wrote:
On Thu, Nov 8, 2012 at 5:54 PM, Thomas Charron twaf...@gmail.com
mailto:twaf...@gmail.com wrote:
On 2.6.31-11-rt (Ubuntu 10.04 realtime kernel)
./a.out starting...
My original scheduling policy is SCHED_OTHER (0)
The original
