NYCPHP Meetup

[Jeff Siegel]

Dan,

Just to clarify things a bit. It was working fine all along. Nothing was 
changed either in the INI file or the location of the tmp directory 
(which is on the same physical drive as the site itself).

Jeff
===================

Daniel Convissor wrote:

>Hi Jeff:
>
>On Tue, Nov 18, 2003 at 09:08:42PM -0500, Jeff Siegel wrote:
>  
>
>>"ERROR NUMBER: 2
>>ERR DETAILS: Failed to write session data (files). Please verify that
>>the current setting of session.save_path is correct (/tmp)"
>>
>>The interesting thing here is the specific error (failure to write
>>session data) even though session.save_path is already set in the
>>php.ini to "/tmp."
>>    
>>
>
>The path in the error message reflects the path in the ini file.  It 
>sounds like you're saying that you're expecting it to be the other way 
>around: that you need to set the ini file to "/tmp" just because the error 
>message says so.
>
>The question is _why_ /tmp wasn't accessible.  Was it working okay until 
>all of a sudden you got this error message?  Or did this message come up 
>as you're trying to initially configure things.  I'm assuming it was a 
>sudden error...
>
>So, is /tmp on the same computer and/or hard drive as the web server?  If
>/tmp is being served from another computer, then it could have been a 
>transient network failure.
>
>To avoid such, change the path to something that's on the same machine as 
>the web server.
>
>See you,
>
>--Dan
>
>  
>