Re: Things I wish I'd known about Inotify

2014-07-28 Thread Michael Kerrisk (man-pages)
On 07/14/2014 01:28 PM, Jan Kara wrote: > On Sat 12-07-14 21:06:45, Michael Kerrisk (man-pages) wrote: >> Late follow up on this thread..., since another question occurred in >> discussions with Jake. >> >> On Fri, Apr 4, 2014 at 2:43 PM, Jan Kara wrote: >>> On Fri 04-04-14 09:35:50, Michael Kerri

Re: Things I wish I'd known about Inotify

2014-07-14 Thread Jan Kara
On Sat 12-07-14 21:06:45, Michael Kerrisk (man-pages) wrote: > Late follow up on this thread..., since another question occurred in > discussions with Jake. > > On Fri, Apr 4, 2014 at 2:43 PM, Jan Kara wrote: > > On Fri 04-04-14 09:35:50, Michael Kerrisk (man-pages) wrote: > >> On 04/03/2014 10:5

Re: Things I wish I'd known about Inotify

2014-07-12 Thread Michael Kerrisk (man-pages)
Late follow up on this thread..., since another question occurred in discussions with Jake. On Fri, Apr 4, 2014 at 2:43 PM, Jan Kara wrote: > On Fri 04-04-14 09:35:50, Michael Kerrisk (man-pages) wrote: >> On 04/03/2014 10:52 PM, Jan Kara wrote: >> > On Thu 03-04-14 08:34:44, Michael Kerrisk (man

Re: Things I wish I'd known about Inotify

2014-04-11 Thread Michael Kerrisk (man-pages)
On 04/07/2014 11:31 AM, Jan Kara wrote: > On Sun 06-04-14 11:00:29, Michael Kerrisk (man-pages) wrote: >> On 04/04/2014 02:43 PM, Jan Kara wrote: >>> On Fri 04-04-14 09:35:50, Michael Kerrisk (man-pages) wrote: On 04/03/2014 10:52 PM, Jan Kara wrote: > On Thu 03-04-14 08:34:44, Michael Ker

Re: Things I wish I'd known about Inotify

2014-04-07 Thread Jan Kara
On Sun 06-04-14 11:00:29, Michael Kerrisk (man-pages) wrote: > On 04/04/2014 02:43 PM, Jan Kara wrote: > > On Fri 04-04-14 09:35:50, Michael Kerrisk (man-pages) wrote: > >> On 04/03/2014 10:52 PM, Jan Kara wrote: > >>> On Thu 03-04-14 08:34:44, Michael Kerrisk (man-pages) wrote: > > [...] > > >>>

Re: Things I wish I'd known about Inotify

2014-04-06 Thread Michael Kerrisk (man-pages)
On 04/04/2014 02:43 PM, Jan Kara wrote: > On Fri 04-04-14 09:35:50, Michael Kerrisk (man-pages) wrote: >> On 04/03/2014 10:52 PM, Jan Kara wrote: >>> On Thu 03-04-14 08:34:44, Michael Kerrisk (man-pages) wrote: [...] Dealing with rename() events The IN_MOVED_FROM and IN_MOV

Re: Things I wish I'd known about Inotify

2014-04-04 Thread Stef Bon
2014-04-03 17:38 GMT+02:00 Eric W. Biederman : > > Other pitfalls. > > Inotify only report events that a user space program triggers through > the filesystem API. Which means inotify is limited for remote > filesystems I'm working on enabling fsnotify for fuse. The sending of a watch/mask to use

Re: Things I wish I'd known about Inotify

2014-04-04 Thread Eric Paris
On Fri, 2014-04-04 at 15:00 +0200, David Herrmann wrote: > 1) > IN_IGNORED is async and _immediate_ in case a file got deleted. So if > you use watch-descriptors as keys for your objects, an _already_ used > key might be returned by inotify_add_watch() if an IN_IGNORED is > queued for the old watc

Re: Things I wish I'd known about Inotify

2014-04-04 Thread David Herrmann
Hi On Fri, Apr 4, 2014 at 3:00 PM, David Herrmann wrote: > 1) > IN_IGNORED is async and _immediate_ in case a file got deleted. So if > you use watch-descriptors as keys for your objects, an _already_ used > key might be returned by inotify_add_watch() if an IN_IGNORED is > queued for the old wat

Re: Things I wish I'd known about Inotify

2014-04-04 Thread David Herrmann
Hi On Thu, Apr 3, 2014 at 8:34 AM, Michael Kerrisk (man-pages) wrote: > With that in mind, I've drafted some substantial additions to the > inotify(7) man page. I would be very happy if folk on the "To:" list > could comment on the text below, since I believe you all have a lot of > practical exp

Re: Things I wish I'd known about Inotify

2014-04-04 Thread Jan Kara
On Fri 04-04-14 09:35:50, Michael Kerrisk (man-pages) wrote: > On 04/03/2014 10:52 PM, Jan Kara wrote: > > On Thu 03-04-14 08:34:44, Michael Kerrisk (man-pages) wrote: > >>Limitations and caveats > >>The inotify API provides no information about the user or process > >>that trig

Re: Things I wish I'd known about Inotify

2014-04-04 Thread Michael Kerrisk (man-pages)
[CC += Al Viro & Linux, since they also discussed the point about remote filesystems and /proc and /sys here: http://thread.gmane.org/gmane.linux.file-systems/83641/focus=83713 .] On 04/03/2014 05:38 PM, Eric W. Biederman wrote: > "Michael Kerrisk (man-pages)" writes: > >> (To: == [the set of pe

Re: Things I wish I'd known about Inotify

2014-04-04 Thread Michael Kerrisk (man-pages)
On 04/03/2014 10:52 PM, Jan Kara wrote: > On Thu 03-04-14 08:34:44, Michael Kerrisk (man-pages) wrote: >>Limitations and caveats >>The inotify API provides no information about the user or process >>that triggered the inotify event. In particular, there is no >>easy

Re: Things I wish I'd known about Inotify

2014-04-03 Thread Jan Kara
On Thu 03-04-14 08:34:44, Michael Kerrisk (man-pages) wrote: >Limitations and caveats >The inotify API provides no information about the user or process >that triggered the inotify event. In particular, there is no >easy way for a process that is monitoring events

Re: Things I wish I'd known about Inotify

2014-04-03 Thread Eric W. Biederman
"Michael Kerrisk (man-pages)" writes: > (To: == [the set of people I believe know a lot about inotify]) > > Hello all, > > Lately, I've been studying the inotify API fairly thoroughly and > realized that there's a very big gap between knowing what the system > calls do versus using them to reliab

Things I wish I'd known about Inotify

2014-04-02 Thread Michael Kerrisk (man-pages)
(To: == [the set of people I believe know a lot about inotify]) Hello all, Lately, I've been studying the inotify API fairly thoroughly and realized that there's a very big gap between knowing what the system calls do versus using them to reliably and efficiently monitor the state of a set of fil