ID: 49503 Updated by: srina...@php.net Reported By: mike at fuelsaver-mpg dot com -Status: Open +Status: Assigned Bug Type: Session related Operating System: Linux 2.6.9-023stab048.6-enterpr PHP Version: 5.2.10 -Assigned To: +Assigned To: srinatar New Comment:
i will assign it to myself so that i can look more into this some time next week Previous Comments: ------------------------------------------------------------------------ [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. ------------------------------------------------------------------------ [2009-09-30 00:11:39] phi...@php.net There was some feedback, status->open. ------------------------------------------------------------------------ [2009-09-18 22:38:38] jd at cpanel dot net Still present in 5.2.11. This looks like it's identical to bugs 49401, 49427 and 49433 which were incorrectly marked as bogus. This happens when the mm session module tries to initialize itself. You don't need anything configured to use MM to hit the problem. As this particular bug illustrates, even a valid session.save_path setting wont avoid running into the same spurious warning. Ex: j...@jd:~$ /usr/local/bin/php -i | grep -i session PHP Warning: PHP Startup: mm_create(0, /session_mm_cli32004) failed, err mm:core: failed to open semaphore file (Permission denied) in Unknown on line 0 session Session Support => enabled session.auto_start => Off => Off session.bug_compat_42 => On => On session.bug_compat_warn => On => On session.cache_expire => 180 => 180 session.cache_limiter => nocache => nocache session.cookie_domain => no value => no value session.cookie_httponly => Off => Off session.cookie_lifetime => 0 => 0 session.cookie_path => / => / session.cookie_secure => Off => Off session.entropy_file => no value => no value session.entropy_length => 0 => 0 session.gc_divisor => 100 => 100 session.gc_maxlifetime => 1440 => 1440 session.gc_probability => 1 => 1 session.hash_bits_per_character => 4 => 4 session.hash_function => 0 => 0 session.name => PHPSESSID => PHPSESSID session.referer_check => no value => no value session.save_handler => files => files session.save_path => no value => no value session.serialize_handler => php => php session.use_cookies => On => On session.use_only_cookies => Off => Off session.use_trans_sid => 0 => 0 WDDX Session Serializer => enabled The change between 5.2.9 and 5.2.10 that makes the difference is the warning added in revision 280733: r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose ------------------------------------------------------------------------ r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2 lines Changed paths: M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c M /php/php-src/branches/PHP_5_2/ext/session/mod_mm.c M /php/php-src/branches/PHP_5_2/ext/session/mod_user.c M /php/php-src/branches/PHP_5_2/ext/session/php_session.h M /php/php-src/branches/PHP_5_2/ext/session/session.c MFH: Sync WS / CS changes where applicable ------------------------------------------------------------------------ It's not really clear why the warning was added to the 5.2 branch though, since it doesn't look like it was added to trunk or 5.3 in revisions 280729 and 280728. svn diff http://svn.php.net/repository/php/php-src/branches/PHP_5_2/ext/session/mod_mm.c http://svn.php.net/repository/php/php-src/trunk/ext/session/mod_mm.c ------------------------------------------------------------------------ [2009-09-17 01:00:02] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ 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/49503 -- Edit this bug report at http://bugs.php.net/?id=49503&edit=1
