Lines Matching refs:on
113 The ``uv_fs_req_cleanup()`` function must always be called on filesystem
208 We start off opening pipes on the files we require. libuv pipes to a file are
211 .. rubric:: uvtee/main.c - read on pipes
237 The read callback ``nread`` parameter is less than 0 on any error. This error
239 function ``uv_close()`` which deals with the handle based on its internal type.
259 does not get passed through to the write callback trigged on write completion. To
269 unknowingly be writing to a pipe. This makes it susceptible to `aborting on
276 .. _aborting on receiving a SIGPIPE: http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#The_speci…
281 All modern operating systems provide APIs to put watches on individual files or
293 Currently this example only works on OSX and Windows.
322 ``UV_FS_EVENT_RECURSIVE`` will start watching subdirectories as well on
328 is the file on which the watch was set.
330 file which was changed. Only non-``null`` on Linux and Windows. May be ``null``
331 even on those platforms.
347 .. [#fsnotify] inotify on Linux, FSEvents on Darwin, kqueue on BSDs,
348 ReadDirectoryChangesW on Windows, event ports on Solaris, unsupported on Cygwin
