Bug #23673
closed
Tagging typo3temp with CACHEDIR.TAG
0%
Description
Tagging the typo3temp directory with an empty file CACHEDIR.TAG will enable tools like tar to recognize that the directory does not need to be processed (using --exclude-caches or --exclude-caches-under for the tar command).
It would be really nice and would save a lot of CPU power and diskspace when pulling backups of TYPO3 installations using any tool which is aware of CACHEDIR.TAG.
Sorry to add this here at the bugtracker but I couldn't find any information about how to submit feature requests such as this one. Hope it's OK.
As an example, my company currently hosts 100+ TYPO3 installations on various servers and I'm currently tagging all typo3temp directories manually to prevent our backup system from including these fairly massive directories in incremental daily backups. I realise this is probably not so commonplace, but is there a chance you could have such a tag be created by the TYPO3 source along with the typo3temp directory itself?
Even better, could this file be touch()'ed when all cache is cleared through the backend, just to be sure it is there at all times?
typo3temp is a cache, after all :)
(issue imported from #M15894)
Updated by Chris topher about 14 years ago
Hi Claus,
first: Yes, this is the right place for a feature request!
You say that you want to use --exclude-caches on that dirs. Wouldn't it be the same, if you used --exclude=typo3temp? There you would not have to add the CACHEDIR.TAG file.
Updated by Claus Due about 14 years ago
Hi Christopher,
Yes, --exclude=typo3temp can also be used, definitely - but this is only half of a proper solid solution, since tagging with CACHEDIR.TAG allows utilities to include the directory itself but exclude any files inside it - which is very useful when restoring, given that the typo3temp-directory needs write-permissions for the httpd-user.
Also, there are other utils which consider the tag before syncing, dumping, copying etc.
One could easily argue that this tagging is a manual task and should be left up to the system administrator, though.
After reading up a bit on CACHEDIR.TAG standards, I found that the file should contain the following line:
Signature: 8a477f597d28d172789f06886806bc55
And can be supplied with comments after this, such as:
Signature: 8a477f597d28d172789f06886806bc55- Cache directory created by TYPO3
Updated by Alexander Opitz about 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0) - Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
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.