Re: [PATCH 00/23] per device dirty throttling -v8
From: Ingo Molnar <hidden>
Date: 2007-08-05 12:59:18
Also in:
lkml
* Alan Cox [off-list ref] wrote:
quoted
The only remotely valid compatibility argument would be Mutt - but even that handles it just fine. (we broke way more software via noexec)And went through a sensible process of resolving it. And its not just mutt. HSM stuff stops working which is a big deal as stuff clogs up. The /tmp/ cleaning tools go wrong as well.
what OSS HSM software stops working and what is its failure mode? /tmp cleaning tools will work _just fine_ if we report back max(mtime,ctime) as atime - they'll zap more /tmp stuff as they used to. There's no guarantee for /tmp contents anyway if tmpwatch is running. Or the patch below. Ingo
--- /etc/cron.daily/tmpwatch.orig 2007-08-05 14:44:25.000000000 +0200
+++ /etc/cron.daily/tmpwatch 2007-08-05 14:45:10.000000000 +0200@@ -1,9 +1,9 @@ #! /bin/sh -/usr/sbin/tmpwatch -x /tmp/.X11-unix -x /tmp/.XIM-unix -x /tmp/.font-unix \ +/usr/sbin/tmpwatch --mtime -x /tmp/.X11-unix -x /tmp/.XIM-unix -x /tmp/.font-unix \ -x /tmp/.ICE-unix -x /tmp/.Test-unix 10d /tmp -/usr/sbin/tmpwatch 30d /var/tmp +/usr/sbin/tmpwatch --mtime 30d /var/tmp for d in /var/{cache/man,catman}/{cat?,X11R6/cat?,local/cat?}; do if [ -d "$d" ]; then - /usr/sbin/tmpwatch -f 30d "$d" + /usr/sbin/tmpwatch --mtime -f 30d "$d" fi done --
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>