The man page confusingly says that the mask is "typically" hexadecimal, when in fact it is always hexadecimal. Fix the language, and provide an additional example with no leading "0x". Signed-off-by: Chris Metcalf <cmetcalf@xxxxxxxxxxxx> --- schedutils/taskset.1 | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/schedutils/taskset.1 b/schedutils/taskset.1 index 901f9faf5f45..6b8146985355 100644 --- a/schedutils/taskset.1 +++ b/schedutils/taskset.1 @@ -51,7 +51,8 @@ to the last logical CPU. Not all CPUs may exist on a given system but a mask may specify more CPUs than are present. A retrieved mask will reflect only the bits that correspond to CPUs physically on the system. If an invalid mask is given (i.e., one that corresponds to no valid CPUs on the current system) an -error is returned. The masks are typically given in hexadecimal. For example, +error is returned. The masks are given in hexadecimal, with or without +a leading "0x". For example, .RS 4 .TP 12 .BR 0x00000001 @@ -62,6 +63,9 @@ is processors #0 and #1, .TP .BR 0xFFFFFFFF is all processors (#0 through #31). +.TP +.BR 32 +is processors #1, #4, and #5. .RE .PP When -- 2.7.2 -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
