$ php --version 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 PHP 5.2.10-pl0-gentoo with Suhosin-Patch 0.9.7 (cli) (built: Aug 25 2009 20:04:48) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies with Suhosin v0.9.27, Copyright (c) 2007, by SektionEins GmbH Reproducible: Always Steps to Reproduce: 1. Run php --version on the command line as example output in "Description" above. 2. 3. Actual Results: $ php --version 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 PHP 5.2.10-pl0-gentoo with Suhosin-Patch 0.9.7 (cli) (built: Aug 25 2009 20:04:48) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies Expected Results: n/a It should not have output the warning exhibited. In addition, phpinfo() output to the browser reports that the Configure Command includes '--disable-cli'. Don't understand why that appears and don't recall if it was there when cli performed without the warning in previous php version compiles. But 'cli' is present in the USE flags list. Also, the Configure Command list includes '--with-mm'.
Uncomment the line ;session.save_path = "/tmp" in the file /etc/php/cli-php5/php.ini As of 5.2.10 the default is /.
(In reply to comment #1) > Uncomment the line > ;session.save_path = "/tmp" > in the file > /etc/php/cli-php5/php.ini > > As of 5.2.10 the default is /. > There's no way they changed the default to that as it doesn't make any sense whatsoever. I've filed a php bug report here: http://bugs.php.net/bug.php?id=49401
Seems it is related to http://bugs.php.net/49503
*** Bug 271053 has been marked as a duplicate of this bug. ***
I'm still looking into this. For the short term you can either: (1) set save_path explicitly. (2) USE="-sharedmem" and emerge -C libmm I didn't have problems without libmm (or with USE="apache2" for that matter) --disable-cli *might* turn up because we're building php a couple of times (for each SAPI you define). So your apache SAPI might not know about your CLI SAPI. But that's just a guess.
(In reply to comment #5) > I'm still looking into this. > > For the short term you can either: > (1) set save_path explicitly. Matti, why don't you set it explicitly to proper value by default? It would solve most of sandbox violations some packages in the tree are suffering due that Thanks
Is this issue still around? It should have been fixed by upstream. At least I cannot reproduce with php-5.3.2
*** Bug 309469 has been marked as a duplicate of this bug. ***
Ole: you testing with USE="-apache2"? I haven't hit that with the apache2 SAPI, a bug report upstream hinted that this SAPI still defaults save_path to /tmp.
I've added a little sed to uncomment ;session.save_path = "/tmp" in the config files. So this should be fixed now (at least I can't reproduce with USE="sharedmem cli -apache2 -cgi" php-5.3.3). Thanks for the comments.
