Without further ado, the following was found: Issue: B<sched_get_priority_min>() POSIX.1 → B<sched_get_priority_min>(). POSIX.1 "The range of scheduling priorities may vary on other POSIX systems, thus it " "is a good idea for portable applications to use a virtual priority range and " "map it to the interval given by B<sched_get_priority_max>() and " "B<sched_get_priority_min>() POSIX.1 requires a spread of at least 32 " "between the maximum and the minimum values for B<SCHED_FIFO> and B<SCHED_RR>."
