Synchronous filesystem operations
This module is independent of lwt. It might be useful, if you target windows:
include Uwt_base.Fs_functions with type 'a t := 'a Uwt_base.uv_resultinclude module type of Uwt_base.Fs_types
with type uv_open_flag = Uwt_base.Fs_types.uv_open_flag
with type file_kind = Uwt_base.Fs_types.file_kind
with type symlink_mode = Uwt_base.Fs_types.symlink_mode
with type access_permission = Uwt_base.Fs_types.access_permission
with type stats = Uwt_base.Fs_types.statstype uv_open_flag = Uwt_base.Fs_types.uv_open_flag = | O_RDONLYOpen for reading
*)| O_WRONLYOpen for writing
*)| O_RDWROpen for reading and writing
*)| O_NONBLOCKOpen in non-blocking mode, ignored on Windows
*)| O_CREATCreate if nonexistent
*)| O_EXCLFail if existing
*)| O_TRUNCTruncate to 0 length if existing
*)| O_APPENDOpen for append
*)| O_NOCTTYDon't make this dev a controlling tty, ignored on Windows
*)| O_DSYNCWrites complete as `Synchronised I/O data integrity completion', ignored by some platforms
*)| O_SYNCWrites complete as `Synchronised I/O file integrity completion', ignored by some platforms
*)| O_RSYNCReads complete as writes (depending on O_SYNC/O_DSYNC), only supported on some Unix platforms, ignored otherwise
*)| O_TEMPORARYwindows only, ignored on Unix
*)| O_SHORT_LIVEDwindows only, ignored on Unix
*)| O_SEQUENTIALwindows only, ignored on Unix
*)| O_RANDOMwindows only, ignored on Unix
*)| O_DIRECTOn Windows supported since libuv 1.16
*)| O_EXLOCKOS X (and Windows, but with different semantic)
*)| O_NOATIMEno windows, some Unix systems, ignored otherwise
*)| O_SYMLINKno windows, some Unix systems, ignored otherwise
*)| O_NOFOLLOWno windows, some Unix systems, ignored otherwise
*)| O_DIRECTORYno windows, some Unix systems, ignored otherwise
*)O_CLOEXEC and O_SHARE_DELETE, O_SHARE_WRITE, O_SHARE_READ don't exist, because these flags are unconditionally added by libuv, if the platform supports them.
type file_kind = Uwt_base.Fs_types.file_kind = type symlink_mode = Uwt_base.Fs_types.symlink_mode = On Windows it can be specified how the symlink will be created:
type access_permission = Uwt_base.Fs_types.access_permission = type stats = Uwt_base.Fs_types.stats = {st_dev : int;st_kind : file_kind;st_perm : int;st_nlink : int;st_uid : int;st_gid : int;st_rdev : int;st_ino : int;st_size : int64;st_blksize : int;st_blocks : int;st_flags : int;st_gen : int;st_atime : int64;st_atime_nsec : int;st_mtime : int64;st_mtime_nsec : int;st_ctime : int64;st_ctime_nsec : int;st_birthtime : int64;st_birthtime_nsec : int;}val openfile :
?perm:int ->
mode:uv_open_flag list ->
string ->
Uwt_base.file Uwt_base.uv_resultEquivalent to open(2).
val read :
?pos:int ->
?len:int ->
Uwt_base.file ->
buf:bytes ->
int Uwt_base.uv_resultread ~pos ~len fd ~buf reads ~len bytes from descriptor fd, storing them in byte sequence buf, starting at position ~pos in ~buf. Return the number of bytes actually read.
val read_ba :
?pos:int ->
?len:int ->
Uwt_base.file ->
buf:Uwt_base.buf ->
int Uwt_base.uv_resultlike read, buf for bigarrays. Bigarrays are passed directly to libuv (no copy to c heap or stack). It's faster, but you must manually ensure, that the bigarray is not accessed from another thread.
val pread :
?pos:int ->
?len:int ->
Uwt_base.file ->
fd_offset:int64 ->
buf:bytes ->
int Uwt_base.uv_resultval pread_ba :
?pos:int ->
?len:int ->
Uwt_base.file ->
fd_offset:int64 ->
buf:Uwt_base.buf ->
int Uwt_base.uv_resultval write :
?pos:int ->
?len:int ->
Uwt_base.file ->
buf:bytes ->
int Uwt_base.uv_resultwrite fd ~pos ~len fd ~buf writes ~len bytes to descriptor fd, taking them from byte sequence buf, starting at position ~pos in ~buf. Return the number of bytes actually written.
val write_string :
?pos:int ->
?len:int ->
Uwt_base.file ->
buf:string ->
int Uwt_base.uv_resultval write_ba :
?pos:int ->
?len:int ->
Uwt_base.file ->
buf:Uwt_base.buf ->
int Uwt_base.uv_resultval pwrite :
?pos:int ->
?len:int ->
Uwt_base.file ->
fd_offset:int64 ->
buf:bytes ->
int Uwt_base.uv_resultval pwrite_string :
?pos:int ->
?len:int ->
Uwt_base.file ->
fd_offset:int64 ->
buf:string ->
int Uwt_base.uv_resultval pwrite_ba :
?pos:int ->
?len:int ->
Uwt_base.file ->
fd_offset:int64 ->
buf:Uwt_base.buf ->
int Uwt_base.uv_resultval writev :
Uwt_base.file ->
Uwt_base.Iovec_write.t list ->
int Uwt_base.uv_resultwrite multiple buffers at once. If the number of buffers is greater than IOV_MAX, newer libuv versions already contains code to circumvent this issue
val pwritev :
Uwt_base.file ->
Uwt_base.Iovec_write.t list ->
int64 ->
int Uwt_base.uv_resultval close : Uwt_base.file -> unit Uwt_base.uv_resultClose a file descriptor.
val unlink : string -> unit Uwt_base.uv_resultdelete a name and possibly the file it refers to
val mkdir : ?perm:int -> string -> unit Uwt_base.uv_resultCreate a directory.
val rmdir : string -> unit Uwt_base.uv_resultDelete an empty directory
val fsync : Uwt_base.file -> unit Uwt_base.uv_resultsynchronize a file's in-core state with storage device.
val fdatasync : Uwt_base.file -> unit Uwt_base.uv_resultval ftruncate : Uwt_base.file -> len:int64 -> unit Uwt_base.uv_resulttruncate a file to a specified length
val stat : string -> stats Uwt_base.uv_resultReturn the information for the named file.
val lstat : string -> stats Uwt_base.uv_resultval fstat : Uwt_base.file -> stats Uwt_base.uv_resultval rename : src:string -> dst:string -> unit Uwt_base.uv_resultchange the name or location of a file
val link : target:string -> link_name:string -> unit Uwt_base.uv_resultlink creates a new link (also known as a hard link) to an existing file
val symlink :
?mode:symlink_mode ->
src:string ->
dst:string ->
unit ->
unit Uwt_base.uv_resultsymlink creates a symbolic link named ~dst which contains the string ~src
val mkdtemp : string -> string Uwt_base.uv_resultThe mkdtemp function generates a uniquely named temporary directory from template. The last six characters of template must be XXXXXX and these are replaced with a string that makes the directory name unique
val sendfile :
?pos:int64 ->
?len:nativeint ->
dst:Uwt_base.file ->
src:Uwt_base.file ->
unit ->
nativeint Uwt_base.uv_resultA limited equivalent to sendfile(2). It copies data between one file descriptor and another
val utime : string -> access:float -> modif:float -> unit Uwt_base.uv_resultutime changes the access and modification times of a file. If both times are 0.0, the access and last modification times are both set to the current time.
val futime :
Uwt_base.file ->
access:float ->
modif:float ->
unit Uwt_base.uv_resultval readlink : string -> string Uwt_base.uv_resultreadlink reads the value of a symbolic link
val access : string -> access_permission list -> unit Uwt_base.uv_resultCheck user's permissions for a file
val chmod : string -> perm:int -> unit Uwt_base.uv_resultChange the permissions of the named file.
val fchmod : Uwt_base.file -> perm:int -> unit Uwt_base.uv_resultChange the permissions of an opened file.
val chown : string -> uid:int -> gid:int -> unit Uwt_base.uv_resultChange the owner ~uid and owner ~gid of the named file.
val fchown : Uwt_base.file -> uid:int -> gid:int -> unit Uwt_base.uv_resultChange the owner ~uid and owner ~gid of the opened file.
val scandir : string -> (file_kind * string) array Uwt_base.uv_resultOn Linux, getting the type of an entry is only supported by some filesystems (btrfs, ext2, ext3 and ext4 at the time of this writing), check the getdents(2) man page.
val realpath : string -> string Uwt_base.uv_resultEquivalent to realpath(3) on Unix. Windows uses GetFinalPathNameByHandle.
Warning This function has certain platform specific caveats that were discovered when used in Node.
macOS and other BSDs: this function will fail with UV_ELOOP if more than 32 symlinks are found while resolving the given path. This limit is hardcoded and cannot be sidestepped.
Windows: while this function works in the common case, there are a number of corner cases where it doesn't:
While this function can still be used, it's not recommended if scenarios such as the above need to be supported.
val copyfile :
?excl:bool ->
src:string ->
dst:string ->
unit ->
unit Uwt_base.uv_resultCopies a file from ~src to ~dst.
If ?excl is true, copyfile() will fail with EEXIST if the destination path already exists. The default behavior is to overwrite the destination if it exists.
Warning: If the destination path is created, but an error occurs while copying the data, then the destination path is removed. There is a brief window of time between closing and removing the file where another process could access the file.