Bug #18382 Updated: php looking for session_mm.sem even though session set to files

ID: 18382 Updated by: nod@bouncing.org Reported By: nod@bouncing.org Status: Bogus Bug Type: Reproducible crash Operating System: suse linux 8 -PHP Version: 4.1.2 +PHP Version: 4.2.1 New Comment: bug is still open with 4.2.1 if you run /usr/bin/php as root it puts a session_mm.sem in tmp with read write only privileges to the root user, thereby disabling other user's ability to run. session.save_handler is still set to files, but is still calling mm. Previous Comments: ------------------------------------------------------------------------ [2002-07-17 01:23:06] sniper@php.net Thank you for taking the time to report a problem with PHP. Unfortunately you are not using a current version of PHP -- the problem might already be fixed. Please download a new PHP version from http://www.php.net/downloads.php If you are able to reproduce the bug with one of the latest versions of PHP, please change the PHP version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of PHP. ------------------------------------------------------------------------ [2002-07-16 20:47:29] nod@bouncing.org /usr/bin/php -h for any unprivileged user. What is happening is that the suse apache server starts up with /tmp/session_mm.sem set to read write only for root, therefore everyone else cannot run a php script when /usr/bin/php is run as root it resets itself to rw for everyone, the question is whether or not /usr/bin/php should be looking for session_mm when sessions are disabled just because it was compiled with it. This bug is with all versions of suse 8.0 including their latest patched version of php and mm, and is probably quite important since even when I upgraded and recompiled to try and solve the bug it still happened. Could this be left open ? since anyone using php on the command line is going to be stuck with it. It has been reported to suse. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=18382&edit=1