mirror of
https://git.rtems.org/rtems-docs/
synced 2025-07-25 06:34:05 +08:00
posix-users/process_creation_and_execution.rst: Update pthread_atfork()
Updates #4713.
This commit is contained in:
parent
4f9e9e522f
commit
8741d2c234
@ -313,16 +313,22 @@ pthread_atfork - Register Fork Handlers
|
|||||||
.. list-table::
|
.. list-table::
|
||||||
:class: rtems-table
|
:class: rtems-table
|
||||||
|
|
||||||
* - ``ENOSYS``
|
* - ``0``
|
||||||
- This routine is not supported by RTEMS.
|
- This routine is a non-functional stub.
|
||||||
|
|
||||||
**DESCRIPTION:**
|
**DESCRIPTION:**
|
||||||
|
|
||||||
This routine is not supported by RTEMS.
|
This routine is non-functional stub.
|
||||||
|
|
||||||
**NOTES:**
|
**NOTES:**
|
||||||
|
|
||||||
NONE
|
The POSIX specification for ``pthread_atfork()`` does not address the behavior
|
||||||
|
when in a single process environment. Originally, the RTEMS implementation
|
||||||
|
returned -1 and set errno to ``ENOSYS``. This was an arbitrary decision
|
||||||
|
part with no basis from the wider POSIX community. The FACE Technical
|
||||||
|
Standard includes profiles without multiple process support and defined
|
||||||
|
the behavior in a single process environment to return 0. Logically, the
|
||||||
|
application can register atfork handlers but they will never be invoked.
|
||||||
|
|
||||||
.. _wait:
|
.. _wait:
|
||||||
|
|
||||||
@ -344,7 +350,7 @@ wait - Wait for Process Termination
|
|||||||
**STATUS CODES:**
|
**STATUS CODES:**
|
||||||
|
|
||||||
.. list-table::
|
.. list-table::
|
||||||
:class: rtems-table
|
|
||||||
|
|
||||||
* - ``ENOSYS``
|
* - ``ENOSYS``
|
||||||
- This routine is not supported by RTEMS.
|
- This routine is not supported by RTEMS.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user