Analysis of Process Mutual Exclusion in PHP and Automatic Semaphore Release

The article presents a PHP code snippet that implements process mutual exclusion using a named semaphore.

<?php<br/>ini_set('display_errors',1);<br/>ini_set('display_startup_errors',1);<br/>error_reporting(-1);<br/><br/>$file = "/www/tp/signal.txt";<br/>$key  = ftok($file, "x");<br/>$semaphore = sem_get($file,1,0666,false);<br/>sem_acquire($semaphore);<br/>echo "hello world";<br/>sleep(20);<br/>

The question raised is why, when two processes run this code simultaneously, the second process is not blocked after the first one ends, and whether the process releases the semaphore automatically.

According to the PHP manual, sem_acquire() blocks by default until the semaphore is obtained, but the documentation also notes that any semaphore acquired but not explicitly released will be automatically released when the request ends, triggering a warning. Therefore, when a PHP process terminates, its held semaphore is released automatically.

At the operating‑system level, all opened named semaphores are automatically closed when the process terminates or when execve(2) is invoked.

In summary, in the given PHP code, the first process’s semaphore is automatically released upon termination, allowing the second process to acquire the released semaphore without being blocked.