logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

posix_spawn_file_actions_destroy.3p (3467B)

    

  1. '\" et
  2. .TH POSIX_SPAWN_FILE_ACTIONS_DESTROY "3P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. posix_spawn_file_actions_destroy,
  12. posix_spawn_file_actions_init
  13. \(em destroy and initialize spawn file actions object
  14. (\fBADVANCED REALTIME\fP)
  15. .SH SYNOPSIS
  16. .LP
  17. .nf
  18. #include <spawn.h>
  19. .P
  20. int posix_spawn_file_actions_destroy(posix_spawn_file_actions_t
  21.     *\fIfile_actions\fP);
  22. int posix_spawn_file_actions_init(posix_spawn_file_actions_t
  23.     *\fIfile_actions\fP);
  24. .fi
  25. .SH DESCRIPTION
  26. The
  27. \fIposix_spawn_file_actions_destroy\fR()
  28. function shall destroy the object referenced by
  29. .IR file_actions ;
  30. the object becomes, in effect, uninitialized. An implementation may
  31. cause
  32. \fIposix_spawn_file_actions_destroy\fR()
  33. to set the object referenced by
  34. .IR file_actions
  35. to an invalid value. A destroyed spawn file actions object can be
  36. reinitialized using
  37. \fIposix_spawn_file_actions_init\fR();
  38. the results of otherwise referencing the object after it has been
  39. destroyed are undefined.
  40. .P
  41. The
  42. \fIposix_spawn_file_actions_init\fR()
  43. function shall initialize the object referenced by
  44. .IR file_actions
  45. to contain no file actions for
  46. \fIposix_spawn\fR()
  47. or
  48. \fIposix_spawnp\fR()
  49. to perform.
  50. .P
  51. A spawn file actions object is as defined in
  52. .IR "\fIposix_spawn_file_actions_addclose\fR\^(\|)".
  53. .P
  54. The effect of initializing an already initialized spawn file actions
  55. object is undefined.
  56. .SH "RETURN VALUE"
  57. Upon successful completion, these functions shall return zero;
  58. otherwise, an error number shall be returned to indicate the error.
  59. .SH ERRORS
  60. The
  61. \fIposix_spawn_file_actions_init\fR()
  62. function shall fail if:
  63. .TP
  64. .BR ENOMEM
  65. Insufficient memory exists to initialize the spawn file actions object.
  66. .P
  67. The
  68. \fIposix_spawn_file_actions_destroy\fR()
  69. function may fail if:
  70. .TP
  71. .BR EINVAL
  72. The value specified by
  73. .IR file_actions
  74. is invalid.
  75. .LP
  76. .IR "The following sections are informative."
  77. .SH EXAMPLES
  78. None.
  79. .SH "APPLICATION USAGE"
  80. These functions are part of the Spawn option and need not be
  81. provided on all implementations.
  82. .SH RATIONALE
  83. Refer to the RATIONALE section in
  84. .IR "\fIposix_spawn_file_actions_addclose\fR\^(\|)".
  85. .SH "FUTURE DIRECTIONS"
  86. None.
  87. .SH "SEE ALSO"
  88. .IR "\fIposix_spawn\fR\^(\|)",
  89. .IR "\fIposix_spawn_file_actions_addclose\fR\^(\|)"
  90. .P
  91. The Base Definitions volume of POSIX.1\(hy2017,
  92. .IR "\fB<spawn.h>\fP"
  93. .br
  94. .\"
  95. .SH COPYRIGHT
  96. Portions of this text are reprinted and reproduced in electronic form
  97. from IEEE Std 1003.1-2017, Standard for Information Technology
  98. -- Portable Operating System Interface (POSIX), The Open Group Base
  99. Specifications Issue 7, 2018 Edition,
  100. Copyright (C) 2018 by the Institute of
  101. Electrical and Electronics Engineers, Inc and The Open Group.
  102. In the event of any discrepancy between this version and the original IEEE and
  103. The Open Group Standard, the original IEEE and The Open Group Standard
  104. is the referee document. The original Standard can be obtained online at
  105. http://www.opengroup.org/unix/online.html .
  106. .PP
  107. Any typographical or formatting errors that appear
  108. in this page are most likely
  109. to have been introduced during the conversion of the source files to
  110. man page format. To report such errors, see
  111. https://www.kernel.org/doc/man-pages/reporting_bugs.html .