#19022 [Com]: PHP Warning: Failed to write session data (files)

From: Date: Fri, 06 Sep 2002 09:39:27 +0000
Subject: #19022 [Com]: PHP Warning: Failed to write session data (files)
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-18565@lists.php.net to get a copy of this message
 ID:               19022
 Comment by:       kivi@picox.se
 Reported By:      phpbugs@mx4k.com
 Status:           Feedback
 Bug Type:         Session related
 Operating System: linux (rh7.3), apache 1.3.26
 PHP Version:      4.2.2
 New Comment:

Trying snapshots isn't an option on production servers..


Previous Comments:
------------------------------------------------------------------------

[2002-09-04 23:22:10] kalowsky@php.net

Then shush up and test a snapshot please :)

------------------------------------------------------------------------

[2002-09-04 22:57:37] ShaneO@alldigitalservices.com.au

lol - I dont care anymore mate - just fix it and im happy

------------------------------------------------------------------------

[2002-09-04 19:11:40] wez@php.net

Shane: please read the following:
http://www.php.net/license/3_0.txt (particularly
the part
in uppercase).

Then read this:
http://www.derickrethans.nl/20020502.php.


------------------------------------------------------------------------

[2002-09-04 18:47:38] ShaneO@alldigitalservices.com.au

Our client just pulled out and i lost my job due to this bug. Thanks
guys

------------------------------------------------------------------------

[2002-09-04 08:41:38] kalowsky@php.net

Yes actually the PREAD functionality in the glibc has been found to be
buggy (this is actually in another bug report as well, I just forget
the number off hand).  It was fixed in the CVS for glibc, but that was
only as of July 2002.  

Regardless, try a snapshot for HEAD dated sometime after this point,
I've taken the PREAD out again.  Post back results.  

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/19022

-- 
Edit this bug report at http://bugs.php.net/?id=19022&edit=1



Thread (75 messages)

« previous php.bugs (#18565) next »