Edit report at http://bugs.php.net/bug.php?id=49503&edit=1
ID: 49503
Comment by: tsisaruk dot v at gmail dot com
Reported by: mike at fuelsaver-mpg dot com
Summary: "failed to open semaphore file"
Status: Closed
Type: Bug
Package: Session related
Operating System: Linux 2.6.9-023stab048.6-enterpr
PHP Version: 5.2.11
New Comment:
I added patch which fix trouble with creating semaphore file in /
directory, if sessions.save_path is undefined. It behaviour now is like
file session handle
Previous Comments:
------------------------------------------------------------------------
[2009-10-08 17:57:56] mike at fuelsaver-mpg dot com
Thank you.
------------------------------------------------------------------------
[2009-10-08 10:34:48] jani@php.net
Thanks for digging this. I have absolutely no idea why I had added this
warning there. Might have been either some debug code I put there while
testing or simply copy'n'paste error gone wild.. :(
I removed it now. And you can of course avoid the warning by setting the
session.save_path properly. :)
------------------------------------------------------------------------
[2009-10-08 10:33:26] svn@php.net
Automatic comment from SVN on behalf of jani
Revision: http://svn.php.net/viewvc/?view=revision&revision=289338
Log: - Fixed bug #49503 (invalid warning for failed semaphore file
creation)
# I have no idea why I had added this. Might have been some debug code..
:(
------------------------------------------------------------------------
[2009-10-02 01:06:00] sriram dot natarajan at gmail dot com
i am just curious - how does this affect writing session to memcached ?
------------------------------------------------------------------------
[2009-10-01 12:36:22] senker at gmail dot com
It also disables writing sessions to memcached, so if you are using
memcached, you have to stick to 5.2.9.
Please escalate this to higher priority, it's unbelievable such
important bug spans over two PHP versions already.
------------------------------------------------------------------------
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/bug.php?id=49503--
Edit this bug report at http://bugs.php.net/bug.php?id=49503&edit=1