POSIX_S...DESTROY(3POSIX)

💅 POSIX_S...DESTROY(3POSIX) — the POSIX Programmer's Manual, bestie

okay so this page lives in the POSIX Programmer's Manual, and before we even get into it, real talk:

This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux. 🫠

so like, don't come for me if Linux does its own thing. check the Linux page. check if it even exists. slay responsibly.

---

✨ NAME ✨

posix_spawn_file_actions_destroy, posix_spawn_file_actions_init — destroy and initialize spawn file actions object (ADVANCED REALTIME)

yes babes we are in the ADVANCED REALTIME section, put some respect on it 👑

---

🌸 SYNOPSIS 🌸

#include <spawn.h>

int posix_spawn_file_actions_destroy(posix_spawn_file_actions_t
    *file_actions);
int posix_spawn_file_actions_init(posix_spawn_file_actions_t
    *file_actions);

two functions, one pointer, we love a minimal API 💖

---

🦋 DESCRIPTION 🦋

okay so posix_spawn_file_actions_destroy() shall destroy the object referenced by file_actions, and like… the object becomes, in effect, uninitialized. gone. spiritually and structurally. ✨

an implementation may cause posix_spawn_file_actions_destroy() to set the object referenced by file_actions to an invalid value. so don't be surprised if it's got weird energy after.

a destroyed spawn file actions object can be reinitialized using posix_spawn_file_actions_init() — glow up era, we can rebuild her 💅

but the results of otherwise referencing the object after it has been destroyed are undefined. undefined bestie. we don't do that. 😭

meanwhile posix_spawn_file_actions_init() shall initialize the object referenced by file_actions to contain no file actions for posix_spawn() or posix_spawnp() to perform. a blank canvas. a fresh face. no notes.

a spawn file actions object is as defined in posix_spawn_file_actions_addclose() — go read that one, iykyk.

also: the effect of initializing an already initialized spawn file actions object is undefined. don't double-init, that's not the vibe. 💀

---

⭐ RETURN VALUE ⭐

upon successful completion, these functions shall return zero; otherwise, an error number shall be returned to indicate the error. zero = iconic. nonzero = something's up, check the number. 🔥

---

💜 ERRORS 💜

the posix_spawn_file_actions_init() function shall fail if:

• ENOMEM — insufficient memory exists to initialize the spawn file actions object. no room bestie, she can't sit with us. 😔

the posix_spawn_file_actions_destroy() function may fail if:

• EINVAL — the value specified by file_actions is invalid. that pointer is not giving what it's supposed to give. 🙈

The following sections are informative.

---

🎀 EXAMPLES 🎀

None.

literally none. that's the whole section. she said nothing and left. 🍓

---

🌈 APPLICATION USAGE 🌈

these functions are part of the Spawn option and need not be provided on all implementations. so like… vibe check your platform first, bestie. 🧚

---

👑 RATIONALE 👑

refer to the RATIONALE section in posix_spawn_file_actions_addclose(). that's it, that's the lore. go read the prequel. 📖

---

🔮 FUTURE DIRECTIONS 🔮

None.

the future is empty and honestly? peaceful. 💅

---

🫶 SEE ALSO 🫶

• posix_spawn(), posix_spawn_file_actions_addclose()

the Base Definitions volume of POSIX.1‐2017, <spawn.h>

---

💖 COPYRIGHT 💖

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

---

and that's the whole page bestie, brought to you by IEEE/The Open Group, 2017 — POSIX_S...DESTROY(3POSIX), signing off. destroy responsibly, init lovingly, and never reference a destroyed object. periodt. 💅✨🌈