Req #49658 [Fbk->NoF]: Default save.session_path and mm_create() warning
Edit report at https://bugs.php.net/bug.php?id=49658&edit=1
ID: 49658
Updated by: php-bugs@lists.php.net
Reported by: jeff at macloue dot com
Summary: Default save.session_path and mm_create() warning
-Status: Feedback
+Status: No Feedback
Type: Feature/Change Request
Package: Session related
Operating System: Slackware 13.0
PHP Version: 5.2.11
New Comment:
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
Previous Comments:
------------------------------------------------------------------------
[2012-03-31 04:28:48] yohgaki@php.net
I didn't get warning with 5.3.11-dev. Do you still have issue?
------------------------------------------------------------------------
[2009-09-24 12:35:08] jeff at macloue dot com
Description:
------------
php -n throws a warning:
PHP Warning: PHP Startup: mm_create(0, /session_mm_cli1000) failed, err mm:core: failed to open
semaphore file (Permission denied) in Unknown on line 0
Expected result:
----------------
This bug was previously submitted as #49401. Despite marked bogus it can be very annoying and also
it doesn't seem logical to make the default built-in configuration to throw a warning on
most/all the platforms.
I also did some investigation on that libmm used by PHP session extension and found that creating
the semaphore file is not a must on many platforms but it is kind of recommended and fail-safe way.
I don't see any big trouble if libmm's semaphores are created in $TMP or /tmp directory
instead of "blank" - at least it will make PHP _safer_ on many platforms without adding
much risks. Of course the best way imho will be to make some ./configure switch for setting default
session.save_path value or smth like that.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=49658&edit=1
Thread (3 messages)