posix_spawn_file_actions_init()

Initialize the spawn file actions object

Synopsis:

#include  <posix_spawn_file_actions.h>

int posix_spawn_file_actions_init(
       posix_spawn_file_actions_t *fact_p);

Arguments:

fact_p: The posix_spawn_file_actions_init() function will initialize a spawn file action object fact_p.

Library:

libc

Use the -l c option to qcc to link against this library. This library is usually included automatically.

The posix_spawn_file_actions_init() function will initialize the object referenced by fact_p to contain no file actions for posix_spawn() or posix_spawnp() to perform. A spawn file actions object is as defined in posix_spawn_file_actions_addclose(). The effect of initializing an already initialized spawn file actions object is undefined.

POSIX indicates that results are undefined when reinitializing an already initialized posix_spawn_file_actions_t object. The QNX implementation defines the behavior as identical to the case when the previous object is destroyed and then reinitialized, which means that it's safe to reinitialize an already initialized posix_spawn_file_actions_t object; however, it doesn't support the re-initialization of a posix_spawn_file_actions_t object without an intervening destruction of the object. Repeated calls to posix_spawn_file_actions_init() with the same posix_spawn_file_actions_t object could result in a memory leak.

The posix_spawn_file_actions_destroy() function will render the posix_spawn_file_actions_t unusable. Before the object can be reused, it must be initialized with posix_spawn_file_actions_init(), which includes calling posix_spawn_file_actions_destroy() on an already destroyed object.

Returns:

Upon successful completion, posix_spawn_file_actions_init() returns zero; otherwise, an error number is returned to indicate the error (errno).

Errors:

EINVAL: For any invalid parameter.
ENOMEM: Insufficient memory exists to initialize the spawn file actions object.
EOK: Success.

Classification:

QNX Neutrino

Safety:
Cancellation point	No
Interrupt handler	Yes
Signal handler	Yes
Thread	Yes