On 2/25/2015 4:12 PM, Peter wrote:
On 23/02/15 18:31, Per Jessen wrote:
Has anyone actually looked at what it is _what_ is filling up {/var}/tmp ?
I've not had time since starting this topic to come back to it and things might remain that way for another couple of days, but what I have just discovered is what is responsible for 98% of all the data consumption in my /tmp: it's Dolphin.
My /tmp contains all sorts, anything dating from the system installation over a year ago: gpg-xxxxxx folders, empty plugtmp-x folders, some SpiderOak stuff, about a dozen systemd-private-xxxxxx folders but those only consuming 112kb in total, lots of Clementine art jpg files, clipboard cache, attachments from Thunderbird and a few downloaded items from Firefox opened with Okular or perhaps other programs. But, the vast majority is contained within 184 folders named dolphinxxxxxx inside the kde-<username> subfolder. About two thirds of these are empty, whilst of the remainder, it's just the entire cached contents of various directories, both those permanently on my system and others from removable devices such as my dumbphone when connected via USB Mass Storage. Of the 5.0GB /tmp currently consumes, 4.9GB is this.
/var/tmp is more moderate, currently at 756MB, most of the bytes being within the kdecache-<username> folders. A couple of plasma_theme_xxx.kcache files take up the majority.
So there are two issues from my own perspective: 1. Why is Dolphin caching all this stuff forever, and is there a setting that governs this or a misconfiguration somewhere? (Note: Though Nepomuk Semantic Desktop is enabled, I have file indexing turned off.) 2. Whilst Dolphin accounts for 98% of the actual data size, there's still thousands of files and folders from elsewhere being held in temp and never being cleaned. Well, perhaps some stuff is being cleaned, that I've yet to find out.
I'll have to look into the previous suggestions for cleaning temp when I get a bit more time.
Thanks for the replies thus far.
Peter
I had questions about the Spideraok files as well. I asked them about them and they responded that anything in /tmp can be deleted upon boot:
This is Dana from SpiderOak Support.
Yes, you can delete the spideroak_inotify_db.xxxxxx files as long as SpiderOak isn't running. As long as SpiderOak isn't running during the time you're deleting the files then you should be fine.
So I put in a delete "r" with an exclamation per the man page to delete these only at boot. Its good to know you've tracked down the bulk of this to caches of dolphinxxxxxx, I can make some custom entries for this. I occasionally surf over to my NAS where I have a large collection of photos and such, and if these are being cached, or even thumbnails, it would be huge. I don't know why the current rules don't take care of those, as these rules should descend to those directories. I'll do some digging and post my settings. I don't want to mess up anything that is actually used, and I don't believe that anything in /tmp has anything to do with either nepomuk or Baloo (the 13.2 replacement there-of). That is in your personal directory, -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org