[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20081120191759.GH31176@sci.fi>
Date:	Thu, 20 Nov 2008 21:17:59 +0200
From:	Ville Syrjälä <syrjala@....fi>
To:	public-mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@...h.gmane.org
Cc:	Evgeniy Polyakov 
	<public-zbr-i6C2adt8DTjR7s880joybQ@...h.gmane.org>,
	Christoph Hellwig <public-hch-jcswGhMUV9g@...h.gmane.org>,
	Robert Love <public-rlove-L7G0xEPcOZbYtjvyW6yDsg@...h.gmane.org>,
	public-linux-api-u79uwXL29TY76Z2rM5mHXA@...h.gmane.org,
	public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@...h.gmane.org,
	Andrew Morton 
	<public-akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@...h.gmane.org>,
	public-john-jueV0HHMeujJJrXXpGQQMAC/G2K4zDHf@...h.gmane.org
Subject: Re: [take 3] Use pid in inotify events.
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@....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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
