Lines Matching refs:file
7 libuv provides a wide variety of cross-platform sync and async file system
12 All file operations are run on the threadpool. See :ref:`threadpool` for information
15 Starting with libuv v1.45.0, some file operations on Linux are handed off to
227 .. c:function:: int uv_fs_close(uv_loop_t* loop, uv_fs_t* req, uv_file file, uv_fs_cb cb)
236 On Windows libuv uses `CreateFileW` and thus the file is always opened
240 .. c:function:: int uv_fs_read(uv_loop_t* loop, uv_fs_t* req, uv_file file, const uv_buf_t bufs[], …
243 the current file offset is used and updated.
254 .. c:function:: int uv_fs_write(uv_loop_t* loop, uv_fs_t* req, uv_file file, const uv_buf_t bufs[],…
257 the current file offset is used and updated.
277 …Equivalent to :man:`mkstemp(3)`. The created file path can be found as a null terminated string at…
278 The file descriptor can be found as an integer at `req->result`.
342 On Linux, getting the type of an entry is only supported by some file systems (btrfs, ext2,
346 .. c:function:: int uv_fs_fstat(uv_loop_t* loop, uv_fs_t* req, uv_file file, uv_fs_cb cb)
366 .. c:function:: int uv_fs_fsync(uv_loop_t* loop, uv_fs_t* req, uv_file file, uv_fs_cb cb)
371 For AIX, `uv_fs_fsync` returns `UV_EBADF` on file descriptors referencing
374 .. c:function:: int uv_fs_fdatasync(uv_loop_t* loop, uv_fs_t* req, uv_file file, uv_fs_cb cb)
378 .. c:function:: int uv_fs_ftruncate(uv_loop_t* loop, uv_fs_t* req, uv_file file, int64_t offset, uv…
384 Copies a file from `path` to `new_path`. Supported `flags` are described below.
402 of time between closing and removing the file where another process
403 could access the file.
423 .. c:function:: int uv_fs_fchmod(uv_loop_t* loop, uv_fs_t* req, uv_file file, int mode, uv_fs_cb cb)
428 .. c:function:: int uv_fs_futime(uv_loop_t* loop, uv_fs_t* req, uv_file file, double atime, double …
492 .. c:function:: int uv_fs_fchown(uv_loop_t* loop, uv_fs_t* req, uv_file file, uv_uid_t uid, uv_gid_…
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.
567 The file is opened in append mode. Before each write, the file offset is
568 positioned at the end of the file.
572 The file is created if it does not already exist.
582 … `FILE_FLAG_NO_BUFFERING <https://docs.microsoft.com/en-us/windows/win32/fileio/file-buffering>`_.
594 The file is opened for synchronous I/O. Write operations will complete once
599 … `FILE_FLAG_WRITE_THROUGH <https://docs.microsoft.com/en-us/windows/win32/fileio/file-buffering>`_.
603 If the `O_CREAT` flag is set and the file already exists, fail the open.
623 Use a memory file mapping to access the file. When using this flag, the
624 file cannot be open multiple times concurrently.
631 Do not update the file access time when the file is read.
654 Open the file in nonblocking mode if possible.
662 optimize file caching.
670 Open the file for read-only access.
674 Open the file for read-write access.
679 use this as a hint to optimize file caching.
687 The file is temporary and should not be flushed to disk if possible.
699 The file is opened for synchronous I/O. Write operations will complete once
704 … `FILE_FLAG_WRITE_THROUGH <https://docs.microsoft.com/en-us/windows/win32/fileio/file-buffering>`_.
708 The file is temporary and should not be flushed to disk if possible.
716 If the file exists and is a regular file, and the file is opened
721 Open the file for write-only access.
