Project

General

Profile

Actions

Bug #20158

closed

t3lib::writeFile() not concurency safe

Added by Alienor.net over 15 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2009-03-11
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Hi,

The function t3lib::writeFile() is not concurency safe hence the usage of t3lib_extMgm::writeCacheFiles() can lead to unusable and buggy typo3conf/temp_CACHED_* files.

In such cases, typo3 frontend is broken and need this files to be removed manually.

t3lib::writeFile() is quite trivial to fix using flock(). If you're interrested in a patch, i can provide one.

Cheers,

(issue imported from #M10658)

Actions #1

Updated by Mathias Schreiber almost 10 years ago

  • Description updated (diff)
  • Status changed from New to Needs Feedback
  • Assignee set to Alienor.net
  • Target version deleted (0)
  • TYPO3 Version changed from 4.2 to 7
  • Is Regression set to No

Do you have a solution at hand that also deals with NFS mounts where flock is not available?

Actions #2

Updated by Alexander Opitz almost 10 years ago

  • TYPO3 Version changed from 7 to 4.2
Actions #3

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF