Manpages - sem_destroy.3p

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.

sem_destroy — destroy an unnamed semaphore

  #include <semaphore.h>
  int sem_destroy(sem_t *sem);

The sem_destroy/() function shall destroy the unnamed semaphore indicated by /sem. Only a semaphore that was created using /sem_init/() may be destroyed using /sem_destroy/(); the effect of calling sem_destroy/() with a named semaphore is undefined. The effect of subsequent use of the semaphore /sem is undefined until sem is reinitialized by another call to /sem_init/().

It is safe to destroy an initialized semaphore upon which no threads are currently blocked. The effect of destroying a semaphore upon which other threads are currently blocked is undefined.

Upon successful completion, a value of zero shall be returned. Otherwise, a value of -1 shall be returned and errno set to indicate the error.

The /sem_destroy/() function may fail if:

EINVAL

The sem argument is not a valid semaphore.

EBUSY

There are currently processes blocked on the semaphore.

The following sections are informative.

None.

None.

None.

None.

/semctl ( )/, /semget ( )/, /semop ( )/, /sem_init ( )/, /sem_open ( )/

The Base Definitions volume of POSIX.1‐2017, <semaphore.h>

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 .