Bug #18382: php looking for session_mm.sem even though session set to files
| From: | nod at bouncing dot org | Date: | Wed, 17 Jul 2002 00:47:30 +0000 |
| Subject: | Bug #18382: php looking for session_mm.sem even though session set to files | ||
| Groups: | php.bugs | ||
| Request: | Send a blank email to php-bugs+get-14356@lists.php.net to get a copy of this message | ||
From: nod@bouncing.org
Operating system: suse linux 8
PHP version: 4.1.2
PHP Bug Type: Reproducible crash
Bug description: php looking for session_mm.sem even though session set to files
/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 bug report at http://bugs.php.net/?id=18382&edit=1
--
Fixed in CVS: http://bugs.php.net/fix.php?id=18382&r=fixedcvs
Fixed in release: http://bugs.php.net/fix.php?id=18382&r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=18382&r=needtrace
Try newer version: http://bugs.php.net/fix.php?id=18382&r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=18382&r=support
Expected behavior: http://bugs.php.net/fix.php?id=18382&r=notwrong
Not enough info: http://bugs.php.net/fix.php?id=18382&r=notenoughinfo
Submitted twice: http://bugs.php.net/fix.php?id=18382&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=18382&r=globals