[RTEMS Project] #4426: clock_nanosleep() may use wrong clock for relative times

[RTEMS trac]

#4426: clock_nanosleep() may use wrong clock for relative times
-----------------------------+------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  defect           |      Status:  assigned
 Priority:  normal           |   Milestone:  6.1
Component:  posix            |     Version:  6
 Severity:  normal           |  Resolution:
 Keywords:                   |  Blocked By:
 Blocking:                   |
-----------------------------+------------------------------
Description changed by Sebastian Huber:

Old description:

> For relative times, the clock identifier is not used to select the clock
> and instead always the CLOCK_REALTIME is used.

New description:

 For relative times, the clock identifier is not used to select the clock
 and instead always the CLOCK_MONOTONIC is used. A side-effect is that
 sleep() and nanosleep() use the wrong clock (CLOCK_MONOTONIC instead of
 CLOCK_REALTIME).

--

--
Ticket URL: <http://devel.rtems.org/ticket/4426#comment:1>
RTEMS Project <http://www.rtems.org/>
RTEMS Project