Here's an excerpt from the docs for the sched_param structure that is returned when you attempt to find your priority 
using the pthread_getschedparam() call:

sched_priority
    When you get the scheduling parameters, this member reflects the priority that was assigned to the thread or process
. It doesn't reflect any temporary adjustments due to priority inheritance.

If you examine a server thread after it has received a message, you'll see that this member *does* change to match the 
client prio.  Why is this?  It seems to contradict the docs, and well as to be counter-intuitive.  I would have guessed 
that this member should stay the same, and the sched_curpriority member should change.

--Chris