Lines Matching refs:a

7 libuv provides a wide variety of cross-platform sync and async file system
8 operations. All functions defined in this document take a callback, which is
17 a (sometimes significant) increase in throughput there should be no change in
169 :c:func:`uv_fs_closedir()`. `dirents` represents a user provided array of
182 Callback called when a request is completed asynchronously.
224 Cleanup request. Must be called after a request is finished to deallocate
247 to build libuv), files opened using ``UV_FS_O_FILEMAP`` may cause a fatal
261 to build libuv), files opened using ``UV_FS_O_FILEMAP`` may cause a fatal
273 …Equivalent to :man:`mkdtemp(3)`. The result can be found as a null terminated string at `req->path…
277 …Equivalent to :man:`mkstemp(3)`. The created file path can be found as a null terminated string at…
288 Opens `path` as a directory stream. On success, a `uv_dir_t` is allocated
308 Iterates over the directory stream, `dir`, returned by a successful
333 Equivalent to :man:`scandir(3)`, with a slightly different API. Once the callback
353 Equivalent to :man:`statfs(2)`. On success, a `uv_statfs_t` is allocated
384 Copies a file from `path` to `new_path`. Supported `flags` are described below.
390 create a copy-on-write reflink. If the underlying platform does not
392 copy-on-write, a fallback copy mechanism based on
395 attempt to create a copy-on-write reflink. If the underlying platform does
401 the data, then the destination path is removed. There is a brief window
455 * ``UV_FS_SYMLINK_DIR``: indicates that `path` points to a directory.
475 * Windows: while this function works in the common case, there are a number of corner cases
546 For a file descriptor in the C runtime, get the OS-dependent handle.
555 For a OS-dependent handle, get the file descriptor in the C runtime.
577 aligned. Buffer size and address should be a multiple of the physical sector
587 If the path is not a directory, fail the open.
595 all data and a minimum of metadata are flushed to disk.
608 be used without `O_CREAT` if pathname refers to a block device. If the
623 Use a memory file mapping to access the file. When using this flag, the
638 If the path identifies a terminal device, opening the path will not cause
647 If the path is a symbolic link, fail the open.
661 Access is intended to be random. The system can use this as a hint to
679 use this as a hint to optimize file caching.
716 If the file exists and is a regular file, and the file is opened