moving kernel threads: "no task matched move criteria"

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use cset on a system where taskset is located in /bin instead of /usr/bin
2. cset proc -k --from root --to system

What is the expected output?
# cset proc -k --from root --to system
cset: moving all kernel threads from / to /system
cset: moving 51 kernel threads to: /system
cset: --> not moving 1154 threads (not unbound, use --force)
[==================================================]%
cset: done

What do you see instead?
# cset proc -k --from root --to system
cset: moving all kernel threads from / to /system
cset: **> no task matched move criteria
cset: done

What version of the product are you using? On what operating system?
cpuset-1.5.6
Red Hat Enterprise Linux Server release 6.4 (Santiago)

Please provide any additional information below.
log shows:
131104-06:26:42 proc   DEBUG     kernel thread 2 not found , perhaps it went 
away
[...]
for all kernel threads found earlier

Problem is in cpuset/commands/proc.py, where "/usr/bin/taskset" is hardcoded.  
There isn't a trivial AND portable fix there, though, except to remove the full 
path in favor of no path and dependence on the PATH environment variable.  
Another option is some sort of autotools thing, (but I'm getting outside my 
comfort area).

Original issue reported on code.google.com by thinkope...@gmail.com on 4 Nov 2013 at 5:49