Bug 272217 - Caches should be saved in home directory, not /var/tmp
Summary: Caches should be saved in home directory, not /var/tmp
Status: RESOLVED NOT A BUG
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: 4.6
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 276466 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-05-02 10:07 UTC by subscryer
Modified: 2011-06-25 13:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description subscryer 2011-05-02 10:07:20 UTC 
Version:           4.6 (using KDE 4.6.2) 
OS:                Linux

I run a system with encrypted home, tmp and swap. Currently kde will save cache data in /var/tmp. Seems like http cache is also written there.
Creating yet another encrypted partition with uncertain size would be a poor solution IMHO.
What I'm asking is that kde sc adopts a policy which restricts writes of personal data only to home (and tmp when it makes sense).
In other words:
.kde4/cache-localhost.localdomain should be a directory
.kde4/cache-$myhostname should be a directory or a symlink to .kde4/cache-localhost.localdomain

Reproducible: Always
Comment 1 Maksim Orlovich 2011-05-02 19:14:58 UTC 
And what if the home directory is on NFS?
Comment 2 subscryer 2011-05-03 09:26:25 UTC 
I'm not sure I understand your objection, I don't see sockets or other special files in those directories.
Do you mean that they should be local to the system? I'd rather keep them within the user's home instead but that's just my opinion.
Comment 3 Dawit Alemayehu 2011-05-24 20:15:30 UTC 
Of course this being KDE that is already configurable. See 4.6 KDETMP and 4.7 KDEVARTMP at
http://techbase.kde.org/KDE_System_Administration/Environment_Variables
Comment 4 Christoph Feck 2011-06-25 13:46:05 UTC 
*** Bug 276466 has been marked as a duplicate of this bug. ***