> > > > Hi, > > > > I wrote a small app yesterday that updates a file by mmapping the > > file (RW), changing the thing around, and then exiting. > > > > This did not trigger a change in the mtime of the file. Thus rsync > > didn't pick up that the file had changed. > > > > I understand that tracking every change to a RW mmapped file is > > costly, and thus unfeasable, but shouldn't then the close cause a > > mtime update? > > > > The server where this happened is running 2.6.21, so my apologies if > > this has already been corrected. > > This is an old bug, don't know if it was fixed or not. Please see > http://lkml.org/lkml/2006/5/17/138
It's not fixed yet, but Anton Salikhmetov is currently working on it: http://lkml.org/lkml/2008/1/15/202 Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
