Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760639AbXHEM7S (ORCPT ); Sun, 5 Aug 2007 08:59:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757263AbXHEM7K (ORCPT ); Sun, 5 Aug 2007 08:59:10 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:56445 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756974AbXHEM7J (ORCPT ); Sun, 5 Aug 2007 08:59:09 -0400 Date: Sun, 5 Aug 2007 14:58:47 +0200 From: Ingo Molnar To: Alan Cox Cc: Claudio Martins , Jeff Garzik , =?iso-8859-1?Q?J=F6rn?= Engel , Linus Torvalds , Peter Zijlstra , linux-mm@kvack.org, Linux Kernel Mailing List , miklos@szeredi.hu, akpm@linux-foundation.org, neilb@suse.de, dgc@sgi.com, tomoki.sekiyama.qu@hitachi.com, nikita@clusterfs.com, trond.myklebust@fys.uio.no, yingchao.zhou@gmail.com, richard@rsk.demon.co.uk, david@lang.hm Subject: Re: [PATCH 00/23] per device dirty throttling -v8 Message-ID: <20070805125847.GC22060@elte.hu> References: <20070803123712.987126000@chello.nl> <46B4E161.9080100@garzik.org> <20070804224706.617500a0@the-village.bc.nu> <200708050051.40758.ctpm@ist.utl.pt> <20070805014926.400d0608@the-village.bc.nu> <20070805072805.GB4414@elte.hu> <20070805134640.2c7d1140@the-village.bc.nu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070805134640.2c7d1140@the-village.bc.nu> User-Agent: Mutt/1.5.14 (2007-02-12) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.0.3 -1.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1563 Lines: 39 * Alan Cox wrote: > > 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/