I kind of understand the temptattion to clear the /tmp directory, in /home/'myuser', but then think heck something must want these files, and leave it be.
That is precisely why rebooting immediately after you've emptied one of the tmp
directories is a good idea.
They are intended for temporary files that don't have to survive a reboot, but those files may be needed by your running programs. If you, on the other hand, find a program that uses the the tmp
directories for permanent storage, you've found one buggy program - which I wouldn't trust to do anything
Also note that PCC makes it easy to move /temp
into RAM, and if you do, it will be emptied every time you shut down your computer.
As some of the more important tmp
) used to be symbolic links to /tmp
in PCLinuxOS, rebooting would in fact empty all of them. (They still are symlinks on all my
systems, but this isn't the default any more. Why? I don't know but I suppose the reason might be security-related. Perhaps It was felt that the sticky bit on /tmp
didn't give the users' temporary files the protection they needed.)
If I use Bleachbit it all seems simpler as I don't have to take responsibility and maybe wrongly assume it will be 'intelligent' deciding what to delete.
Which leads to Bleachbit; if I select KDE, or System /temp, generally my desktop will crash (freeze) requiring logging out/in a few times.
I wonder what programs cause this ? Or is it a quirk of using MiniMe ? It's been very hot, please excuse if i've wandered off the track.