when trying to use the "taskset" utility to specifiy processor affinity for a new or already running process, taskset returns with error messages that, to me at least, do not indicate where the error is. I know that the error is not in syntax. I'm running the latest gentoo-dev-sources kernel and the latest schedutils, which I have emerged twice just in case. If taskset is run on an already running PID, the following occurs: computer:/> taskset -p 01 9881 sched_getaffinity: Bad file descriptor failed to get pid 9881's affinity computer:/> If taskset is run on a new process, then the following occurs: computer:/>taskset 01 ls sched_setaffinity: Bad address failed to set pid 0's affinity. computer:/> The same commands executed on a RedHat system perform as expected, running schedutils 1.3. All commands are being executed on AMD dual Opteron systems. Reproducible: Always Steps to Reproduce: 1. execute taskset on a running or new process 2. taskset returns an error 3. Actual Results: it returned an error Expected Results: it should have stated the previous affinity, and the new affinity.
1.3.5 fixes this bug.
1.3.5 has been marked stable in cvs. Thanks for noticing
