Inotify: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
→‎Usage: This section pretty much goes against WP:NOTMANUAL
Redundant formatting
Line 1: Line 1:
{{lowercase}}
{{Lowercase title}}

'''Inotify''' ([[inode]] notify) is a [[Linux kernel]] subsystem that acts to extend [[filesystem]]s to notice changes to the filesystem, and report those changes to applications. It replaces an earlier facility, [[dnotify]], which had similar goals.
'''Inotify''' ([[inode]] notify) is a [[Linux kernel]] subsystem that acts to extend [[filesystem]]s to notice changes to the filesystem, and report those changes to applications. It replaces an earlier facility, [[dnotify]], which had similar goals.


Inotify was created by [[John McCutchan]],<ref name="inotify-patch">{{cite web | url = http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/6366aaa10cb23bcc/a54e97d545ad66fe | title = fa.linux.kernal post '''[RFC][PATCH] inotify 0.8''' | date = 2004-07-29 | accessdate = 2013-08-19}}</ref> and it was merged into the [[Linux kernel mainline]] in kernel version 2.6.13, released on August 29, 2005;<ref name="kernelnewbies">[http://kernelnewbies.org/Linux_2_6_13 Linux 2.6.13, kernelnewbies.org]</ref> later kernel versions included further improvements. The required library interfaces were added into the [[GNU C Library]] (glibc) in its version 2.4, released in March 2006, while the support for inotify was completed in glibc version 2.5, released in September 2006.<ref name="man-page">[http://man7.org/linux/man-pages/man7/inotify.7.html inotify man page]</ref>
Inotify was created by [[John McCutchan]],<ref name="inotify-patch">{{cite web | url = http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/6366aaa10cb23bcc/a54e97d545ad66fe | title = fa.linux.kernal post [RFC][PATCH] inotify 0.8 | date = 2004-07-29 | accessdate = 2013-08-19}}</ref> and it was merged into the [[Linux kernel mainline]] in kernel version 2.6.13, released on August 29, 2005;<ref name="kernelnewbies">[http://kernelnewbies.org/Linux_2_6_13 Linux 2.6.13, kernelnewbies.org]</ref> later kernel versions included further improvements. The required library interfaces were added into the [[GNU C Library]] (glibc) in its version 2.4, released in March 2006, while the support for inotify was completed in glibc version 2.5, released in September 2006.<ref name="man-page">[http://man7.org/linux/man-pages/man7/inotify.7.html inotify man page]</ref>


One major use is in [[desktop search]] utilities like [[Beagle (software)|Beagle]], where its functionality permits [[Index (search engine)|reindexing]] of changed files without scanning the filesystem for changes every few minutes, which would be very inefficient. By being ''told'' directly by the kernel that a file has changed, indexing utilities can achieve change-to-reindexing times of only about a second.{{Citation needed|date = November 2014}}
One major use is in [[desktop search]] utilities like [[Beagle (software)|Beagle]], where its functionality permits [[Index (search engine)|reindexing]] of changed files without scanning the filesystem for changes every few minutes, which would be very inefficient. By being told directly by the kernel that a file has changed, indexing utilities can achieve change-to-reindexing times of only about a second.{{Citation needed|date = November 2014}}


Inotify can also be used to automatically update directory views, reload configuration files, log changes, backup, synchronize, and upload.
Inotify can also be used to automatically update directory views, reload configuration files, log changes, backup, synchronize, and upload.
Line 23: Line 24:


== {{Anchor|FANOTIFY}}Advantages over dnotify ==
== {{Anchor|FANOTIFY}}Advantages over dnotify ==
There are a number of advantages when using ''inotify'' when compared to the older [[dnotify]] API that it replaced.<ref name=lwn-inotify>{{cite web |author=[[Michael Kerrisk]] |date={{date|2014-07-14}} |title=Filesystem notification, part 2: A deeper investigation of inotify |publisher=[[LWN.net]] |url=https://lwn.net/SubscriberLink/605128/19d8b7ae42dfc036/ }}</ref><ref>[http://www.developertutorials.com/tutorials/linux/monitor-linux-inotify-050531/page2.html Why inotify?]</ref><ref>[http://www.kernel.org/pub/linux/kernel/people/rml/inotify/README ''inotify'' README file]</ref> With dnotify, a program had to use one [[file descriptor]] for each directory that it was monitoring. This can become a bottleneck since the limit of file descriptors per process could be reached. Later, ''fanotify'' was created to overcome this issue. The use of file descriptors along with dnotify also proved to be a problem when using removable media. Devices could not be unmounted since file descriptors kept the resource busy.
There are a number of advantages when using inotify when compared to the older [[dnotify]] API that it replaced.<ref name=lwn-inotify>{{cite web |author=[[Michael Kerrisk]] |date={{date|2014-07-14}} |title=Filesystem notification, part 2: A deeper investigation of inotify |publisher=[[LWN.net]] |url=https://lwn.net/SubscriberLink/605128/19d8b7ae42dfc036/ }}</ref><ref>[http://www.developertutorials.com/tutorials/linux/monitor-linux-inotify-050531/page2.html Why inotify?]</ref><ref>[http://www.kernel.org/pub/linux/kernel/people/rml/inotify/README inotify README file]</ref> With dnotify, a program had to use one [[file descriptor]] for each directory that it was monitoring. This can become a bottleneck since the limit of file descriptors per process could be reached. Later, fanotify was created to overcome this issue. The use of file descriptors along with dnotify also proved to be a problem when using removable media. Devices could not be unmounted since file descriptors kept the resource busy.


Another drawback of ''dnotify'' is the level of granularity, since programmers can only monitor changes at the directory level. To access detailed information about the environmental changes that occur when a notification message is sent, a stat structure must be used; this is considered a necessary evil in that a cache of stat structures has to be maintained, for every new stat structure generated a comparison is run against the cached one.
Another drawback of dnotify is the level of granularity, since programmers can only monitor changes at the directory level. To access detailed information about the environmental changes that occur when a notification message is sent, a stat structure must be used; this is considered a necessary evil in that a cache of stat structures has to be maintained, for every new stat structure generated a comparison is run against the cached one.


The ''inotify'' API uses fewer file descriptors, allowing programmers to use the established select and poll interface, rather than the signal notification system used by [[dnotify]]. This also makes integration with existing select- or poll-based libraries (like [[GLib]]) easier.
The inotify API uses fewer file descriptors, allowing programmers to use the established select and poll interface, rather than the signal notification system used by [[dnotify]]. This also makes integration with existing select- or poll-based libraries (like [[GLib]]) easier.


== See also ==
== See also ==

Revision as of 19:46, 7 July 2015


Inotify (inode notify) is a Linux kernel subsystem that acts to extend filesystems to notice changes to the filesystem, and report those changes to applications. It replaces an earlier facility, dnotify, which had similar goals.

Inotify was created by John McCutchan,[1] and it was merged into the Linux kernel mainline in kernel version 2.6.13, released on August 29, 2005;[2] later kernel versions included further improvements. The required library interfaces were added into the GNU C Library (glibc) in its version 2.4, released in March 2006, while the support for inotify was completed in glibc version 2.5, released in September 2006.[3]

One major use is in desktop search utilities like Beagle, where its functionality permits reindexing of changed files without scanning the filesystem for changes every few minutes, which would be very inefficient. By being told directly by the kernel that a file has changed, indexing utilities can achieve change-to-reindexing times of only about a second.[citation needed]

Inotify can also be used to automatically update directory views, reload configuration files, log changes, backup, synchronize, and upload.

Limitations

Limitations imposed by inotify include the following:

  • Inotify does not support recursively watching directories, meaning that a separate inotify watch must be created for every subdirectory.[4]
  • Inotify does report some but not all events in sysfs and procfs.
  • Notification via inotify requires the kernel to be aware of all relevant filesystem events, which is not always possible for networked filesystems such as NFS where changes made by one client are not immediately broadcast to other clients.
  • Rename events are not handled directly; i.e., inotify issues two separate events that must be examined and matched in a context of potential race conditions.

History

  • July 2004: the first release announcement[1]
  • August 29, 2005: Linux kernel version 2.6.13 released, containing merged inotify code[2]
  • March 2006: GNU C Library (glibc) version 2.4 released, bringing initial inotify support[3]
  • September 2006: Glibc version 2.5 released, bringing complete inotify support[3]

Advantages over dnotify

There are a number of advantages when using inotify when compared to the older dnotify API that it replaced.[5][6][7] With dnotify, a program had to use one file descriptor for each directory that it was monitoring. This can become a bottleneck since the limit of file descriptors per process could be reached. Later, fanotify was created to overcome this issue. The use of file descriptors along with dnotify also proved to be a problem when using removable media. Devices could not be unmounted since file descriptors kept the resource busy.

Another drawback of dnotify is the level of granularity, since programmers can only monitor changes at the directory level. To access detailed information about the environmental changes that occur when a notification message is sent, a stat structure must be used; this is considered a necessary evil in that a cache of stat structures has to be maintained, for every new stat structure generated a comparison is run against the cached one.

The inotify API uses fewer file descriptors, allowing programmers to use the established select and poll interface, rather than the signal notification system used by dnotify. This also makes integration with existing select- or poll-based libraries (like GLib) easier.

See also

References

  1. ^ a b "fa.linux.kernal post [RFC][PATCH] inotify 0.8". 2004-07-29. Retrieved 2013-08-19.
  2. ^ a b Linux 2.6.13, kernelnewbies.org
  3. ^ a b c inotify man page
  4. ^ Robert Love, Linux system programming. O'Reilly, p. 236
  5. ^ Michael Kerrisk (14 July 2014). "Filesystem notification, part 2: A deeper investigation of inotify". LWN.net.
  6. ^ Why inotify?
  7. ^ inotify README file

External links

Retrieved from "https://en.wikipedia.org/w/index.php?title=Inotify&oldid=670410552"