Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756773AbYKTUur (ORCPT ); Thu, 20 Nov 2008 15:50:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754749AbYKTUui (ORCPT ); Thu, 20 Nov 2008 15:50:38 -0500 Received: from blaine.gmane.org ([80.91.229.8]:54031 "EHLO hugh.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752727AbYKTUuh convert rfc822-to-8bit (ORCPT ); Thu, 20 Nov 2008 15:50:37 -0500 Date: Thu, 20 Nov 2008 21:17:59 +0200 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= To: public-mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@hugh.gmane.org Cc: Evgeniy Polyakov , Christoph Hellwig , Robert Love , public-linux-api-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org, public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org, Andrew Morton , public-john-jueV0HHMeujJJrXXpGQQMAC/G2K4zDHf@hugh.gmane.org Subject: Re: [take 3] Use pid in inotify events. Message-ID: <20081120191759.GH31176@sci.fi> Mail-Followup-To: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= , mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, Evgeniy Polyakov , Christoph Hellwig , Robert Love , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Andrew Morton , john-jueV0HHMeujJJrXXpGQQMAC/G2K4zDHf@public.gmane.org References: <20081116232450.GA13547@ioremap.net> <20081118131937.GC16944@lst.de> <20081119140500.GA25968@ioremap.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Content-Transfer-Encoding: 8BIT X-TMDA-Confirmed: Thu, 20 Nov 2008 21:50:27 +0100 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1016 Lines: 26 On Wed, Nov 19, 2008 at 09:43:41AM -0500, Michael Kerrisk wrote: > I think what is really needed at this point is some consideration of > what other extensions (if any) might be desired for inotify, and how > we might be best create a design that suits those and future needs. In case people are taking notes for "inotify ng" I have one improvement request. Add some way to know when a move event is complete. Currently if you're just wathing the source or target directory of a move you only get one of the MOVED_FROM/MOVED_TO events. Not knowing whether you'll eventually receive the other half of the event is problematic when you want to treat such unpaired events the same as DELETE/CREATE events. -- Ville Syrj?l? syrjala@sci.fi http://www.sci.fi/~syrjala/ -- 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/