sem_remove() shouldn't be part of a normal cleanup/teardown and should be called very rarely due to bugs in the implementation.
It doesn't seem to hurt to leave semaphores lying around and is likely to be more performance-friendly to do so. If you are concerned about having too many semaphores floating around for an application (e.g. a file cache that uses ftok()), you can use some modulus arithmetic and simple addition to create a limited range of values for your semaphores off in the middle of nowhere. For example, ftok() % 101 + 0xBADBEEF. Be sure to replace 0xBADBEEF with your own random value. The example limits the range to 101 semaphores. 101 is a prime number - so if you want more or less, be sure to replace it with a prime number since primes theoretically help distribute values more evenly.
sem_remove
(PHP 4 >= 4.1.0, PHP 5, PHP 7, PHP 8)
sem_remove — Détruit un sémaphore
Description
sem_remove() supprime le sémaphore donné.
Après suppression du sémaphore, il n'est plus utilisable.
Valeurs de retour
Cette fonction retourne true en cas de succès ou false si une erreur survient.
Historique
| Version | Description |
|---|---|
| 8.0.0 |
semaphore attend désormais une SysvSemaphore;
auparavant, une resource était attendue.
|
Voir aussi
- sem_get() - Retourne un identifiant de sémaphore
- sem_release() - Libère un sémaphore
- sem_acquire() - Réserve un sémaphore
add a note
User Contributed Notes 1 note
donotcallme at iwillcallyou dot com ¶
11 years ago
