| … | |
… | |
| 1600 | semantics of C<ev_stat> watchers, which means that libev sometimes needs |
1600 | semantics of C<ev_stat> watchers, which means that libev sometimes needs |
| 1601 | to fall back to regular polling again even with inotify, but changes are |
1601 | to fall back to regular polling again even with inotify, but changes are |
| 1602 | usually detected immediately, and if the file exists there will be no |
1602 | usually detected immediately, and if the file exists there will be no |
| 1603 | polling. |
1603 | polling. |
| 1604 | |
1604 | |
|
|
1605 | =head3 ABI Issues (Largefile Support) |
|
|
1606 | |
|
|
1607 | Libev by default (unless the user overrides this) uses the default |
|
|
1608 | compilation environment, which means that on systems with optionally |
|
|
1609 | disabled large file support, you get the 32 bit version of the stat |
|
|
1610 | structure. When using the library from programs that change the ABI to |
|
|
1611 | use 64 bit file offsets the programs will fail. In that case you have to |
|
|
1612 | compile libev with the same flags to get binary compatibility. This is |
|
|
1613 | obviously the case with any flags that change the ABI, but the problem is |
|
|
1614 | most noticably with ev_stat and largefile support. |
|
|
1615 | |
| 1605 | =head3 Inotify |
1616 | =head3 Inotify |
| 1606 | |
1617 | |
| 1607 | When C<inotify (7)> support has been compiled into libev (generally only |
1618 | When C<inotify (7)> support has been compiled into libev (generally only |
| 1608 | available on Linux) and present at runtime, it will be used to speed up |
1619 | available on Linux) and present at runtime, it will be used to speed up |
| 1609 | change detection where possible. The inotify descriptor will be created lazily |
1620 | change detection where possible. The inotify descriptor will be created lazily |
