El dom 22 jun 2014 17:49:30 CLT, John Andersen escribió:
On 06/22/2014 03:45 AM, C wrote:
On Sat, Jun 21, 2014 at 11:35 PM, Jan Ritzerfeld
wrote: Am Samstag, 21. Juni 2014, 22:18:57 schrieb C:
What is the "right" way to clean up /tmp? [...]
SInce 12.3 and systemd: https://www.suse.com/releasenotes/i386/openSUSE/12.3/RELEASE-NOTES.en.html#s...
There is an age parameter, see man tmpfiles.d
I wrote a few words about the underlying mechanism some months ago: http://lists.opensuse.org/opensuse/2014-02/msg00545.html
Thanks for the advice everyone. I've cleaned up the /tmp and it seems to be less out of control now. I still have to poke about in my /usr/lib and see what's lurking there that I'm not using and I could clear out (using zypper of course). I'm back to +/-2 to 3 GB of my usual typical install size. That's a bit more... comfortable :-)
C
So can anyone explain why the exclusion lines in /etc/tmp.conf # Exclude namespace mountpoints created with PrivateTmp=yes X /tmp/systemd-private-* X /var/tmp/systemd-private-*
What are these directory entries, of which I have well over 300, some dating back years (12.3 system).
What are they,
This are directories where systemd sets up a private /tmp namespace, so services can't "see" or modify each other temporary files. Since the handling of temporary files is sometimes buggy and in many occasions this kind of bugs are security related, many services set PrivateTmp=true
and why are they excluded from cleaning?
Because they are managed exclusively by systemd. note that old systemd versions didn't properly garbage collected this directories, that is probably the reason you have very old ones around. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org