man complex (from release 3.18) contains the following code:
complex z = cexp(I * pi);
Reading the C99 standard, "complex" is not a valid type, and several
compilers (Intel ICC, ARM RVCT) will refuse to compile.
It should be
double complex z = cexp(I * pi);
instead.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The word "signal" was duplicated in NOTES, and the RETURN
section refers to setjmp() and sigsetjmp(), and mentions
longjmp(), but not siglongjmp().
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Starting with Linux 2.6.30, the MS_RELATIME behavior became
the default, and MS_STRICTATIME is required to obtain the
traditional semantics.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Some bit rot had crept in regarding the discussion of the
number of arguments in older versions of this syscall.
Simplify the text to just say that Linux 2.4 and earlier
didn't have ptid, tls, and ctid arguments.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533868
Reported-by: Shachar Shemesh <shachar@debian.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As reported by Motohiro:
"man poll" describe this error code.
>ERRORS
> EBADF An invalid file descriptor was given in one of the sets.
but current kernel implementation ignore invalid file descriptor,
not return EBADF.
...
In the other hand, SUSv3 talk about
> POLLNVAL
> The specified fd value is invalid. This flag is only valid in the
> revents member; it shall ignored in the events member.
and
> If the value of fd is less than 0, events shall be ignored, and
> ireevents shall be set to 0 in that entry on return from poll().
but, no desribe EBADF.
(see http://www.opengroup.org/onlinepubs/009695399/functions/poll.html)
So, I think the implementation is correct.
Why don't we remove EBADF description?
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Reported-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Gallmeister and Lewine are rather old books. Probably,
there are better books to consult nowadays, and anyway,
this man page isn't intended to be a bibliography.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
It was noted on lkml that the fork behaviour is documented
for the POSIX AIO calls, but not for the Linux native calls.
Here is a patch which adds a small blurb that folks will
hopefully find useful.
Upon fork(), the child process does not inherit the
io_context_t data structures returned by io_setup,
and thus cannot submit further asynchronous I/O or
reap event completions for said contexts.
Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Alexander Lamaison pointed out that this is not obvious
from the documentation, citing an example with passing the
FILE * handle to a function that tries to fstat() its
fileno() in order to determine the buffer size.
Reported-by: Alexander Lamaison <awl03@doc.ic.ac.uk>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Michael Kerrisk