Description:
------------
PHP 5.2.1 and forward (I think) breaks under the FastCGI/apache proc manager.  When the parent is launched, it fails to open the socket due to trying to open the socket in a directory that doesn't allow it.  If I compare two traces of an older version (5.2.0) and the newer version (running 5.2.4):

Working:

/var/tmp/fastcgi.out:1786:      unlink("session_mm_cgi-fcgi3357.sem")           = 0
/var/tmp/fastcgi.out:1786:      open("session_mm_cgi-fcgi3357.sem", O_RDWR|O_CREAT, 0600) = 3

Broken:

/var/tmp/fastcgi1.out:1648:     unlink("/session_mm_cli4416.sem")               Err#2 ENOENT
/var/tmp/fastcgi1.out:1648:     open("/session_mm_cli4416.sem", O_RDWR|O_CREAT, 0600) Err#13 EACCES

Note that this puts the "/" in place, which is a bad assumption.

Is it possible this is related to bug 42815 in some way?  It's more severe, in that php won't even run, though.

Reproduce code:
---------------
PHP fails to start.

Expected result:
----------------
I think that this should be hard-coded to a /tmp directory, or else somewhere else that the php process will have the ability to write to.  Unless there's a way to fix this behavior with a correct php.ini setup.  We're running with vhosts and suexec, so the owner of the php process manager won't be able to write to the ServerRoot or the root filesystem (nor do we want it to!)