ID: 13490
Updated by: lobbin
Old Summary: Semaphores don't release automatically
Reported By: [EMAIL PROTECTED]
Old Status: Feedback
Status: Closed
Bug Type: Semaphore related
Operating System: FreeBSD 4.1.1
PHP Version: 4.0.6
New Comment:

-> Closed.


Previous Comments:
------------------------------------------------------------------------

[2002-01-14 07:37:24] [EMAIL PROTECTED]

Checked on FreeBSD 4.4 with PHP 4.1.0 - it works!

------------------------------------------------------------------------

[2002-01-14 02:29:30] [EMAIL PROTECTED]

Is this reproducable on 4.1.1?

------------------------------------------------------------------------

[2002-01-13 20:27:43] [EMAIL PROTECTED]

My bad. Re-opened.

------------------------------------------------------------------------

[2002-01-13 14:52:51] [EMAIL PROTECTED]

http://www.php.net/manual/ru/function.sem-acquire.php:
"After processing a request, any semaphores acquired by the process but
not explicitly released will be released automatically and a warning
will be generated."

Therefore, it is NOT intended behaviour, because in my situation
semaphores DON'T release automatically. And any failure in php script
causes apache to hang up in few seconds, because semaphore is acquired
by dead script and all other instances can't work. This really is bug.
:-(

------------------------------------------------------------------------

[2002-01-13 08:35:48] [EMAIL PROTECTED]

This is intended behaviour. This is how semaphores work. =)
Use sem_remove() to remove semaphores.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/?id=13490


Edit this bug report at http://bugs.php.net/?id=13490&edit=1


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to