Re: File monitor rewrite: Solaris (and other) help wanted
- From: Morten Welinder <mortenw gnome org>
- To: Ryan Lortie <desrt desrt ca>
- Cc: Gtk+ Developers <gtk-devel-list gnome org>
- Subject: Re: File monitor rewrite: Solaris (and other) help wanted
- Date: Thu, 15 Jan 2015 10:59:01 -0500
That does leave tracker-like software in a bad position.
Although I guess one could lobby the kernel people for an inotify
event when a file is mapped and use it as a kind of a hint that the
file should be revisited at some later point.
Morten
On Thu, Jan 15, 2015 at 10:51 AM, Ryan Lortie <desrt desrt ca> wrote:
hi,
On Thu, Jan 15, 2015, at 10:49, Morten Welinder wrote:
Great plan, but you cannot get that in a meaningful way. Think
creat
write
mmap
close
# Further writes by way of the mapped region
I don't think you can detect the end of that write.
Quoting inotify(7):
The inotify API does not report file accesses and modifications
that may
occur because of mmap(2), msync(2), and munmap(2).
so this is a completely lost cause anyway.
Cheers
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]