SEM_POST(3POSIX)

πŸ’– SEM_POST(3POSIX) πŸ’–

okay bestie so this is sem_post from the POSIX Programmer's Manual, and I need you to know right off the bat: this page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ β€” so if you're on Linux, go check the corresponding Linux manual page for the real tea on Linux behavior. Or honestly, the interface might not even be implemented on Linux at all. πŸ™ˆ


✨ PROLOG ✨

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.


πŸŽ€ NAME πŸŽ€

sem_post β€” unlock a semaphore. that's it. that's the girl. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <semaphore.h>

int sem_post(sem_t *sem);

🌸 DESCRIPTION 🌸

okay so sem_post() shall unlock the semaphore referenced by sem by performing a semaphore unlock operation on that semaphore. iconic behavior.

If the semaphore value resulting from this operation is positive, then no threads were blocked waiting for the semaphore to become unlocked β€” the semaphore value is simply incremented. no drama, just math. ✨

If the value of the semaphore resulting from this operation is zero, then one of the threads blocked waiting for the semaphore shall be allowed to return successfully from its call to sem_wait(). 🫢

If the Process Scheduling option is supported, the thread to be unblocked shall be chosen in a manner appropriate to the scheduling policies and parameters in effect for the blocked threads. In the case of the schedulers SCHED_FIFO and SCHED_RR, the highest priority waiting thread shall be unblocked, and if there is more than one highest priority thread blocked waiting for the semaphore, then the highest priority thread that has been waiting the longest shall be unblocked. (first come first served but make it ✨priority✨)

If the Process Scheduling option is not defined, the choice of a thread to unblock is unspecified. like, nobody knows, don't ask. πŸ’€

If the Process Sporadic Server option is supported, and the scheduling policy is SCHED_SPORADIC, the semantics are as per SCHED_FIFO above.

The sem_post() function shall be async-signal-safe and may be invoked from a signal-catching function. yesss she's safe to call from a signal handler, no cap. πŸ”₯


πŸ‘‘ RETURN VALUE πŸ‘‘

If successful, the sem_post() function shall return zero; otherwise, the function shall return -1 and set errno to indicate the error. periodt.


πŸ’… ERRORS πŸ’…

The sem_post() function may fail if:

  • EINVAL β€” the sem argument does not refer to a valid semaphore. 🚩

The following sections are informative.


🌈 EXAMPLES 🌈

See sem_timedwait(). that's the whole section bestie, go look over there. πŸŽ€


⭐ APPLICATION USAGE ⭐

None.


πŸ’œ RATIONALE πŸ’œ

None.


🧚 FUTURE DIRECTIONS 🧚

None.


πŸ“ SEE ALSO πŸ“

  • semctl()
  • semget()
  • semop()
  • sem_timedwait()
  • sem_trywait()

The Base Definitions volume of POSIX.1‐2017, Section 4.12, Memory Synchronization, <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 .


okay that's the whole page, mwah πŸ’‹ β€” this one's brought to you by IEEE/The Open Group, 2017 (the SEM_POST(3POSIX) era, we love her). go unlock something, bestie πŸ¦‹βœ¨