… | |
… | |
1796 | to exchange stat structures with application programs compiled using the |
1796 | to exchange stat structures with application programs compiled using the |
1797 | default compilation environment. |
1797 | default compilation environment. |
1798 | |
1798 | |
1799 | =head3 Inotify and Kqueue |
1799 | =head3 Inotify and Kqueue |
1800 | |
1800 | |
1801 | When C<inotify (7)> support has been compiled into libev (generally only |
1801 | When C<inotify (7)> support has been compiled into libev (generally |
|
|
1802 | only available with Linux 2.6.25 or above due to bugs in earlier |
1802 | available with Linux) and present at runtime, it will be used to speed up |
1803 | implementations) and present at runtime, it will be used to speed up |
1803 | change detection where possible. The inotify descriptor will be created lazily |
1804 | change detection where possible. The inotify descriptor will be created |
1804 | when the first C<ev_stat> watcher is being started. |
1805 | lazily when the first C<ev_stat> watcher is being started. |
1805 | |
1806 | |
1806 | Inotify presence does not change the semantics of C<ev_stat> watchers |
1807 | Inotify presence does not change the semantics of C<ev_stat> watchers |
1807 | except that changes might be detected earlier, and in some cases, to avoid |
1808 | except that changes might be detected earlier, and in some cases, to avoid |
1808 | making regular C<stat> calls. Even in the presence of inotify support |
1809 | making regular C<stat> calls. Even in the presence of inotify support |
1809 | there are many cases where libev has to resort to regular C<stat> polling, |
1810 | there are many cases where libev has to resort to regular C<stat> polling, |