established using
.BR pthread_atfork (3).
.\" and does some magic to ensure that getpid(2) returns the right value.
+.SS Async-signal safety
+.BR _Fork (3)
+is an async-signal safe variant of
+.BR fork (2).
.SH STANDARDS
-POSIX.1-2008.
+POSIX.1-2024.
.SH HISTORY
POSIX.1-2001, SVr4, 4.3BSD.
.SH NOTES
.BR vfork (2),
.BR wait (2),
.BR daemon (3),
+.BR _Fork (3),
.BR pthread_atfork (3),
.BR capabilities (7),
.BR credentials (7)
\f[B]fdatasync\f[](2)
\f[B]fexecve\f[](3) Added in POSIX.1-2008
\f[B]ffs\f[](3) Added in POSIX.1-2008 TC2
-\f[B]fork\f[](2) See notes below
+\f[B]_Fork\f[](3)
\f[B]fstat\f[](2)
\f[B]fstatat\f[](2) Added in POSIX.1-2008
\f[B]fsync\f[](2)
.BR siglongjmp (3)
and the program subsequently calls an unsafe function,
then the behavior of the program is undefined.
-.IP \[bu]
-POSIX.1-2001 TC1 clarified
-that if an application calls
-.BR fork (2)
-from a signal handler and any of the fork handlers registered by
-.BR pthread_atfork (3)
-calls a function that is not async-signal-safe, the behavior is undefined.
-A future revision of the standard
-.\" http://www.opengroup.org/austin/aardvark/latest/xshbug3.txt
-is likely to remove
-.BR fork (2)
-from the list of async-signal-safe functions.
.\"
.IP \[bu]
Asynchronous signal handlers that call functions which are cancelation