On Thursday 24 October 2013, Cristian Rodríguez wrote:
El 24/10/13 13:41, Ruediger Meier escribió:
On Thursday 24 October 2013, Cristian Rodríguez wrote:
El 24/10/13 06:32, Ruediger Meier escribió:
Finally /etc/cron.daily/suse.de-clean-tmp was removed with no replacement and settings in /etc/sysconfig/cron are ignored now just to break existing setups.
as it should..that was all pretty bad actually.
Why bad?
because it was non programable by individual packages and it was papering over bugs in other applications that leave files around.
If any existing file in tmp cause another applications to fail then it's a bug in that application.
How this could be non-sense if it's NEVER cleaned up? How you know my /tmp size and my quota settings?
Well, if you are doing something insane then empty directories might fill up your filesystem..
So the content is always deleted but not the dir itself?
lol thats really flexible. You suggest to download 5 GB new distro packages, and to exchange every single file in /usr to fix something which has always worked in past.
No, what I am telling you is that, yes, it was a non-critical implementation error, that went along because systemd defaults (which we do not use in this case) assumes that at startup /tmp is tmpfs and that you will at least reboot the machine for a kernel update once in a while.
Yeah it's known that systemd defaults are supposed to work on grandmothers cell phone which has weak battery anyways.
I am also telling you it is not a major concern and that it has been already fixed in 13.1.
13.1 is not a release yet. 12.3 is the most recent one. Just fix that bug for 12.3. and stop stupid arguing that's impossible or not important. You are one of the guys who told us that systemd is the better design - this is a situation where you can show us how easy it is to setup things like they should be. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org