IMO you’ll be able to erase every one of.cache with no long haul detrimental consequences to answer the question. If your.cache keeps growing large, it may be easier to go through the contents and determine what app is which makes it large and re-configure a bad working application (as opposed to only removing.cache when it grows too large). Another directory that may use up a lot of space (and/or conserve an uncomfortable little evidence) will be the.thumbs index. Many documents in.thumbs appear to be clones. To scrub (simply take treatment with all the -rf hole and other directories;) It is difficult to know what it is possible to and may not delete in your home index when you’re new-to Ubuntu Linux. For the most part you are able to eliminate most something at home listing, programs or programs that need.cache (or other dot documents for example.local) will re create them. Most of the moment you will reduce custom options, but actual injury to the device. I’d not counsel you begin a routine of trashing issues you may not understand at home listing, back it up or use a check consideration.
If in question, the secure issue should be to make up a back or move the record. If required after that you can restore from backup,. Undoubtedly don’t begin eliminating points you don’t comprehend outside your house index. It’s not usually dangerous to remove it. You might wish to shut all graphical programs (e.g. Banshee, rhythmbox, vlc, application-middle. ) to prevent any distress of the programs opening the cache (where did my report move most of an unexpected!?). It can simply have a measurement of 100+ MB, so get it done, if you need to http://macrush.net take back space.
As currently stated by BretD McCall. The type of files are partial packages, visitor cache, press files like designs, etc, used-to increase future usage of the records that are identical. Another thing to take into account: eliminating an application doesn’t necessarily delete the appropriate /.cache/removed prog file; those files simply take house and therefore are not used in cases like this,. Those can definitely be removed. Responded Sep 28’12 at 20:54 If you /.cache, better to wipe everything at once (so you add /.cache is still managing in the background). & ndash January 11 at 3:57 I would advise not removing it. I’m not just a Linux specialist (however I hope to become!) and don’t know the essentials of the filesystem construction, however, you may study what is inside the folder by going into your home file and reaching ctrl+h to exhibit hidden versions.
You find out what’s in there and can then get inside the.cache folder. Just from the quick glance on my process I am aware that banshee merchants cd art while in the cache folder (do not know why specifically), chrome has info while in the cache folder, a great deal of programs maintain records while in the.cache folder, as well as other material. I am unsure if these records are simply there briefly for speed boost functions (like browser cache) or if this “cache” includes documents for some additional purpose (whilst the pace boost of visitor cache is to counteract extreme usage of bandwidth by re-accessing records on the host, while there ought to be no discernible distinction in r/t moments to get a different report site about the hard-disk). I hope somebody may give a greater reaction to you and understands more about any of it than I really do. Should you add something else you may consider I simply unearthed that my backup drive was filling up with stuff from.cache (I assume purposes are cleaning their own cache, but I actually don’t delete backups therefore it is getting massive). And so I’m excluding but I noticed that.cache has material software I had ignored I actually employed, from TEN YEARS AGO! Everything will be deleted by this in your.cache that has been last reached higher than a year ago If you are worried about managing it, you will be shown by this what is likely to be deleted: I’m using’accessibility time’ for that,’formation time’ might try by using -ctime.