Edit report at https://bugs.php.net/bug.php?id=63908&edit=1

 ID:                 63908
 Updated by:         ras...@php.net
 Reported by:        awm086 at gmail dot com
 Summary:            file_put_contents is not atomic.
 Status:             Not a bug
 Type:               Bug
 Package:            Filesystem function related
 Operating System:   LINUX
 PHP Version:        Irrelevant
 Block user comment: N
 Private report:     N

 New Comment:

You mean tempnam and no, not at all. tempnam() creates an empty file, it 
doesn't 
put anything in it. You can't check disk space, create a file and write to it, 
all in one atomic operation.


Previous Comments:
------------------------------------------------------------------------
[2013-01-07 23:48:20] awm086 at gmail dot com

I noticed that function tempname does the same thing. Is that the case?

------------------------------------------------------------------------
[2013-01-06 00:33:34] ras...@php.net

http://lxr.php.net/xref/PHP_5_4/ext/standard/file.c#564

------------------------------------------------------------------------
[2013-01-06 00:24:42] awm086 at gmail dot com

Where can I find the C implementation of the function. I am just curious now.

------------------------------------------------------------------------
[2013-01-06 00:09:16] ras...@php.net

Nope, sorry, there isn't. The false indicates that the function wasn't able to 
complete its operation. Much like the underlying filesystem calls, there is no 
such thing as transactions or anything along those lines where you can group a 
bunch of operations into a single atomic unit. That's simply not how filesystem 
operations work.

------------------------------------------------------------------------
[2013-01-05 23:40:34] awm086 at gmail dot com

I cannot belive that a function returns false, indicating that a file failed to 
be 
written, and still write to the file system. There must be a way.

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


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

    https://bugs.php.net/bug.php?id=63908


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

Reply via email to