On 6/23/2014 12:15 AM, C wrote:
On Mon, Jun 23, 2014 at 9:02 AM, Basil Chupin <blchupin@iinet.net.au> wrote:
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 :-)
Well, doing what Cristian suggested has decreased my /tmp from 33GB down to 612Kb, and /var/tmp is now only 209MB from (?), ie I didn't take a note of (but it was 'really, really big', I am sure :-D ).
I'm wondering.. what changed. In previous releases, I never had to bother with the size of /tmp. It managed itself quite nicely and didn't grow out of control.
What changed? SystemD. SystemD happened, and it decided it had to take care of cleaning directories instead of allowing the cronjob do it. Why was this necessary? SystemD's mission was to make booting faster. Why in gods name does it have to mess with Cleaning of directories and do such a poor job of it? I'd like to hear a good rational for that. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org