Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751195AbaDREQF (ORCPT ); Fri, 18 Apr 2014 00:16:05 -0400 Received: from mail-we0-f178.google.com ([74.125.82.178]:52198 "EHLO mail-we0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750830AbaDREQC (ORCPT ); Fri, 18 Apr 2014 00:16:02 -0400 MIME-Version: 1.0 In-Reply-To: <20140417212834.GC17769@csclub.uwaterloo.ca> References: <20140417212834.GC17769@csclub.uwaterloo.ca> From: Michael Kerrisk Date: Fri, 18 Apr 2014 06:15:40 +0200 X-Google-Sender-Auth: _PiCd56PMc3TpJ-g40jYD-RR--0 Message-ID: Subject: Re: inotify, new idea? To: Lennart Sorensen Cc: Jos Huisken , Linux Kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 17, 2014 at 11:28 PM, Lennart Sorensen wrote: > On Thu, Apr 17, 2014 at 11:00:37PM +0200, Jos Huisken wrote: >> I was trying to maintain a local and remote directory in sync with >> lsync, using inotify. >> I happen to have >4M files and >400k directories... running over >> /proc/sys/fs/inotify/max_user_watches > > Would fanotify perhaps be a better interface to use? (One of us is misunderstanding fanotify; it might be me.) Did you look at fanotify closely? I don't think it could be used for this task -- does not notify linka dn unlink events, difficult to set up recursive monitoring, etc. Cheers, Michael -- 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/