Lines Matching refs:stat

2620 C<stat> on that path in regular intervals (or when the OS says it changed)
2622 if it did. Starting the watcher C<stat>'s the file, so only changes that
2627 exist" (or more correctly "path cannot be stat'ed") is signified by the
2629 least one) and all the other fields of the stat buffer having unspecified
2637 portable implementation simply calls C<stat(2)> regularly on the path
2645 This watcher type is not meant for massive numbers of stat watchers,
2658 support disabled by default, you get the 32 bit version of the stat
2668 to exchange stat structures with application programs compiled using the
2680 making regular C<stat> calls. Even in the presence of inotify support
2681 there are many cases where libev has to resort to regular C<stat> polling,
2683 many bugs), the path exists (i.e. stat succeeds), and the path resides on
2692 =head3 C<stat ()> is a synchronous operation
2695 the process. The exception are C<ev_stat> watchers - those call C<stat
2699 busy or the intervals between stat's are large, a stat call will be fast,
2703 For networked file systems, calling C<stat ()> can block an indefinite
2704 time due to network issues, and even under good conditions, a stat call
2710 =head3 The special problem of stat time resolution
2712 The C<stat ()> system call only supports full-second resolution portably,
2720 stat data does change in other ways (e.g. file size).
2756 Updates the stat buffer immediately with new values. If you change the
2765 C<ev_statdata>, this is usually the (or one of the) C<struct stat> types
2768 some error while C<stat>ing the file.
4169 =item w->update () (C<ev::stat> only)