That's how I read it as well... Hopefully someone knows for positive... If there were any platforms using it, and they used the test framework, we'd know: the test would take decades :)
It's an easy fix, but indicative that these functions have clearly not been clearly vetted enough. > On Apr 5, 2017, at 10:25 AM, Branko Čibej <br...@apache.org> wrote: > > On 05.04.2017 14:16, Jim Jagielski wrote: >> Hmmm.... Looking over the timed stuff, it seems that semtimedop() >> is used incorrectly. >> >> For both pthread_mutex_timedlock() and sem_timedwait(), the >> timeout variable is the actual wallclock time that the wait >> expires (eg: now+5mins). But, from what I can read about semtimedop(), its >> timeout really is a timeout (5mins). But it seems that we use it >> as if it was wall-clock time, which is WAY wrong... >> >> Can someone check to see what exactly the timeout value is for >> semtimedop()? Is it a delta or a wall-clock? > > > My man page says: > > semtimedop() behaves identically to semop() except that in those > cases where the calling thread would sleep, the duration of that > sleep is limited by the amount of elapsed time specified by the > timespec structure whose address is passed in the timeout argument. > > > Looks like delta to me. > > -- Brane
