incorrect clock_nanosleep.2

incorrect clock_nanosleep.2

[Yuri Kozlov]

Hello.

Next two paragraph is contradict.

If the call is interrupted by a signal handler, clock_nanosleep() returns
-1, and sets errno to EINTR.

And below:
RETURN VALUE
       On successfully sleeping for the requested interval,
       clock_nanosleep() returns 0.  If the call is interrupted by a
       signal handler or encounters an error, then it returns a positive
       error number.

So, return value is positive or -1 ?


-- 
Best Regards,
Yuri Kozlov

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: incorrect clock_nanosleep.2

[Michael Kerrisk]

Hello Yuri,

On Thu, Aug 12, 2010 at 7:59 AM, Yuri Kozlov <yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org> wrote:
> Hello.
>
> Next two paragraph is contradict.
>
> If the call is interrupted by a signal handler, clock_nanosleep() returns
> -1, and sets errno to EINTR.
>
> And below:
> RETURN VALUE
>       On successfully sleeping for the requested interval,
>       clock_nanosleep() returns 0.  If the call is interrupted by a
>       signal handler or encounters an error, then it returns a positive
>       error number.
>
> So, return value is positive or -1 ?

Thanks. This was in fact independently reported a few weeks ago, and
this fix was applied:

--- a/man2/clock_nanosleep.2
+++ b/man2/clock_nanosleep.2
@@ -124,9 +124,7 @@ that terminates the process.

 If the call is interrupted by a signal handler,
 .BR clock_nanosleep ()
-returns \-1, and sets
-.I errno
-to
+fails with the error
 .BR EINTR .
 In addition, if
 .I remain

Cheers,

Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html