package lwt
- Sleeping
- Operations on file-descriptors
- Process handling
- Basic file input/output
- Seeking and truncating
- Syncing
- File status
- File operations on large files
- Operations on file names
- File permissions and ownership
- Operations on file descriptors
- Directories
- Pipes and redirections
- Symbolic links
- Locking
- User id, group id
- Signals
- Sockets
- Host and protocol databases
- Terminal interface
- Configuration (deprecated)
- Low-level interaction
- Notifications
- System threads pool
- CPUs
- Versioned interfaces
Install
dune-project
Dependency
Authors
Maintainers
Sources
md5=279024789a0ec84a9d97d98bad847f97
sha512=698875bd3bfcd5baa47eb48e412f442d289f9972421321541860ebe110b9af1949c3fbc253768495726ec547fe4ba25483cd97ff39bc668496fba95b2ed9edd8
doc/lwt.unix/Lwt_unix/index.html
Module Lwt_unixSource
Cooperative system calls
This modules maps system calls, like those of the standard library's Unix module, to cooperative ones, which will not block the program.
The semantics of all operations is the following: if the action (for example reading from a file descriptor) can be performed immediately, it is performed and returns an already resolved promise, otherwise it returns a pending promise which is resolved when the operation completes.
Most operations on sockets and pipes (on Windows it is only sockets) are cancelable, meaning you can cancel them with Lwt.cancel. For example if you want to read something from a file descriptor with a timeout, you can cancel the action after the timeout and the reading will not be performed if not already done.
For example, consider that you have two sockets sock1 and sock2. You want to read something from sock1 or exclusively from sock2 and fail with an exception if a timeout of 1 second expires, without reading anything from sock1 and sock2, even if they become readable in the future.
Then you can do:
Lwt.pick
[Lwt_unix.timeout 1.0;
read sock1 buf1 ofs1 len1;
read sock2 buf2 ofs2 len2]In this case, it is guaranteed that exactly one of the three operations will complete, and the others will be cancelled.
Same as Unix.handle_unix_error but catches lwt-level exceptions
Sleeping
sleep d is a promise that remains in a pending state for d seconds after which it is resolved with value ().
yield () is a promise in a pending state. It resumes itself as soon as possible and resolves with value ().
auto_pause timeout returns a function f, and f () has the following behavior:
- If it has been more than
timeoutseconds since the last timef ()behaved likeLwt.pause,f ()callsLwt.pause. - Otherwise, if it has been less than
timeoutseconds,f ()behaves likeLwt.return_unit, i.e. it does not yield.
Exception raised by timeout operations
timeout d is a promise that remains pending for d seconds and then is rejected with Timeout.
with_timeout d f is a short-hand for:
Lwt.pick [Lwt_unix.timeout d; f ()]Operations on file-descriptors
The abstract type for file descriptors. A Lwt file descriptor is a pair of a unix file descriptor (of type Unix.file_descr) and a state.
A file descriptor may be:
- opened, in which case it is fully usable
- closed or aborted, in which case it is no longer usable
type state = | Opened(*The file descriptor is opened
*)| Closed| Aborted of exn(*The file descriptor has been aborted, the only operation possible is
*)close, all others will fail.
State of a file descriptor
state fd returns the state of fd.
Returns the underlying unix file descriptor. It always succeeds, even if the file descriptor's state is not Opened.
Wraps a Unix file descriptor fd in an Lwt file_descr fd'.
~blocking controls the internal strategy Lwt uses to perform I/O on the underlying fd. Regardless of ~blocking, at the API level, Lwt_unix.read, Lwt_unix.write, etc. on fd' always block the Lwt promise, but never block the whole process. However, for performance reasons, it is important that ~blocking match the actual blocking mode of fd.
If ~blocking is not specified, of_unix_file_descr chooses non-blocking mode for Unix sockets, Unix pipes, and Windows sockets, and blocking mode for everything else. Note: not specifying ~blocking causes fstat to be lazily called on fd, the first time your code performs I/O on fd'. This fstat call can be expensive, so if you use of_unix_file_descr a lot, be sure to specify ~blocking explicitly.
of_unix_file_descr runs a system call to set the specified or chosen blocking mode on the underlying fd.
To prevent of_unix_file_descr from running this system call, you can pass ~set_flags:false. Note that, in this case, if ~blocking, whether passed explicitly or chosen by Lwt, does not match the true blocking mode of the underlying fd, I/O on fd' will suffer performance degradation.
Note that ~set_flags is effectively always false if running on Windows and fd is not a socket.
Generally, non-blocking I/O is faster: for blocking I/O, Lwt typically has to run system calls in worker threads to avoid blocking the process. See your system documentation for whether particular kinds of file descriptors support non-blocking I/O.
blocking fd indicates whether Lwt is internally using blocking or non-blocking I/O with fd.
Note that this may differ from the blocking mode of the underlying Unix file descriptor (i.e. unix_file_descr fd).
See of_unix_file_descr for details.
set_blocking fd b causes Lwt to internally use blocking or non-blocking I/O with fd, according to the value of b.
If ~set_flags is true (the default), Lwt also makes a system call to set the underlying file descriptor's blocking mode to match. Otherwise, set_blocking is only informational for Lwt.
It is important that the underlying file descriptor actually have the same blocking mode as that indicated by b.
See of_unix_file_descr for details.
abort fd exn makes all current and further uses of the file descriptor fail with the given exception. This put the file descriptor into the Aborted state.
If the file descriptor is closed, this does nothing, if it is aborted, this replace the abort exception by exn.
Note that this only works for reading and writing operations on file descriptors supporting non-blocking mode.
Process handling
fork () does the same as Unix.fork. You must use this function instead of Unix.fork when you want to use Lwt in the child process, even if you have not started using Lwt before the fork.
Notes:
- In the child process all pending
Lwt_unixI/O jobs are abandoned. This may cause the child's copy of their associated promises to remain forever pending. - If you are going to use Lwt in the parent and the child, it is a good idea to call
Lwt_io.flush_allbefore calllingforkto avoid double-flush. - Otherwise, if you will not use Lwt in the child, call
Lwt_main.Exit_hooks.remove_allto avoid Lwt callingLwt_main.runduring process exit. - None of the above is necessary if you intend to call
exec. Indeed, in that case, it is not even necessary to useLwt_unix.fork. You can useUnix.fork. - To abandon some more promises, see
Lwt_main.abandon_yielded_and_paused.
Wrapper for Unix.wait
A promise-returning analog to Unix.waitpid. This call is non-blocking on Unix-like systems, but is always blocking on Windows.
Resource usages
wait4 flags pid returns (pid, status, rusage) where (pid, status) is the same result as Unix.waitpid flags pid, and rusage contains accounting information about the child.
On windows it will always returns { utime = 0.0; stime = 0.0 }.
Returns the number of promises waiting for a child process to terminate.
Executes the given command, waits until it terminates, and return its termination status. The string is interpreted by the shell /bin/sh on Unix and cmd.exe on Windows. The result WEXITED 127 indicates that the shell couldn't be executed.
Basic file input/output
The file descriptor for standard input.
The file descriptor for standard output.
The file descriptor for standard error.
Wrapper for Unix.openfile.
Close a file descriptor. This close the underlying unix file descriptor and set its state to Closed.
read fd buf ofs len reads up to len bytes from fd, and writes them to buf, starting at offset ofs. The function immediately evaluates to an Lwt promise which waits for the operation to complete. If it completes successfully, the promise resolves to the number of bytes actually read, or zero if the end of file has been reached.
Note that the Lwt promise waits for data (or end of file) even if the underlying file descriptor is in non-blocking mode. See of_unix_file_descr for a discussion of non-blocking I/O and Lwt.
If Lwt is using blocking I/O on fd, read writes data into a temporary buffer, then copies it into buf.
The promise can be rejected with any exception that can be raised by Unix.read, except Unix.Unix_error Unix.EAGAIN, Unix.Unix_error Unix.EWOULDBLOCK or Unix.Unix_error Unix.EINTR.
pread fd buf ~file_offset ofs len on file descriptors allowing seek, reads up to len bytes from fd at offset file_offset from the beginning of the file, and writes them to buf, starting at offset ofs.
On Unix systems, the file descriptor position is unaffected. On Windows it is changed to be just after the last read position.
The promise can be rejected with any exception that can be raised by read or lseek.
write fd buf ofs len writes up to len bytes to fd from buf, starting at buffer offset ofs. The function immediately evaluates to an Lwt promise which waits for the operation to complete. If the operation completes successfully, the promise resolves to the number of bytes actually written, which may be less than len.
Note that the Lwt promise waits to write even if the underlying file descriptor is in non-blocking mode. See of_unix_file_descr for a discussion of non-blocking I/O and Lwt.
If Lwt is using blocking I/O on fd, buf is copied before writing.
The promise can be rejected with any exception that can be raised by Unix.single_write, except Unix.Unix_error Unix.EAGAIN, Unix.Unix_error Unix.EWOULDBLOCK or Unix.Unix_error Unix.EINTR.
pwrite fd buf ~file_offset ofs len on file descriptors allowing seek, writes up to len bytes to fd from buf, starting at buffer offset ofs. The data is written at offset file_offset from the beginning of fd.
On Unix systems, the file descriptor position is unaffected. On Windows it is changed to be just after the last written position.
The promise can be rejected with any exception that can be raised by write or lseek.
See write.
See pwrite.
Sequences of buffer slices for writev.
readv fd vs reads bytes from fd into the buffer slices vs. If the operation completes successfully, the resulting promise resolves to the number of bytes read.
Data is always read directly into Bigarray slices. If the Unix file descriptor underlying fd is in non-blocking mode, data is also read directly into bytes slices. Otherwise, data for bytes slices is first read into temporary buffers, then copied.
Note that the returned Lwt promise is pending until failure or a successful read, even if the underlying file descriptor is in non-blocking mode. See of_unix_file_descr for a discussion of non-blocking I/O and Lwt.
If IO_vectors.system_limit is Some n and the count of slices in vs exceeds n, then Lwt_unix.readv reads only into the first n slices of vs.
Not implemented on Windows. It should be possible to implement, upon request, for Windows sockets only.
See readv(3p).
writev fd vs writes the bytes in the buffer slices vs to the file descriptor fd. If the operation completes successfully, the resulting promise resolves to the number of bytes written.
If the Unix file descriptor underlying fd is in non-blocking mode, writev does not make a copy the bytes before writing. Otherwise, it copies bytes slices, but not Bigarray slices.
Note that the returned Lwt promise is pending until failure or a successful write, even if the underlying descriptor is in non-blocking mode. See of_unix_file_descr for a discussion of non-blocking I/O and Lwt.
If IO_vectors.system_limit is Some n and the count of slices in vs exceeds n, then Lwt_unix.writev passes only the first n slices in vs to the underlying writev system call.
Not implemented on Windows. It should be possible to implement, upon request, for Windows sockets only.
The behavior of writev when vs has zero slices depends on the system, and may change in future versions of Lwt. On Linux, writev will succeed and write zero bytes. On BSD (including macOS), writev will fail with Unix.Unix_error (Unix.EINVAL, "writev", ...).
See writev(3p).
Returns whether the given file descriptor is currently readable.
Returns whether the given file descriptor is currently writable.
Waits (without blocking other promises) until there is something to read from the file descriptor.
Note that you don't need to use this function if you are using Lwt I/O functions for reading, since they provide non-blocking waiting automatically.
The intended use case for this function is interfacing with existing libraries that are known to be blocking.
Waits (without blocking other promises) until it is possible to write on the file descriptor.
Note that you don't need to use this function if you are using Lwt I/O functions for writing, since they provide non-blocking waiting automatically.
The intended use case for this function is interfacing with existing libraries that are known to be blocking.
Seeking and truncating
Wrapper for Unix.lseek
Wrapper for Unix.truncate
Wrapper for Unix.ftruncate
Syncing
Synchronise all data and metadata of the file descriptor with the disk. On Windows it uses FlushFileBuffers.
Synchronise all data (but not metadata) of the file descriptor with the disk.
Note that fdatasync is not available on Windows and OS X.
File status
type stats = Unix.stats = {st_dev : int;st_ino : int;st_kind : file_kind;st_perm : file_perm;st_nlink : int;st_uid : int;st_gid : int;st_rdev : int;st_size : int;st_atime : float;st_mtime : float;st_ctime : float;
}Wrapper for Unix.lstat
Wrapper for Unix.fstat
file_exists name tests if a file named name exists.
Note that file_exists behaves similarly to Sys.file_exists:
- “file” is interpreted as “directory entry” in this context
file_exists namewill returnfalsein circumstances that would makestatraise aUnix.Unix_errorexception.
utimes path atime mtime updates the access and modification times of the file at path. The access time is set to atime and the modification time to mtime. To set both to the current time, call utimes path 0. 0..
This function corresponds to Unix.utimes. See also utimes(3p).
Wrapper for Unix.isatty
File operations on large files
Operations on file names
Wrapper for Unix.unlink
Wrapper for Unix.rename
File permissions and ownership
Wrapper for Unix.chmod
Wrapper for Unix.fchmod
Wrapper for Unix.chown
Wrapper for Unix.fchown
Wrapper for Unix.access
Operations on file descriptors
Wrapper for Unix.dup
Wrapper for Unix.dup2
Wrapper for Unix.set_close_on_exec
Wrapper for Unix.clear_close_on_exec
Directories
Wrapper for Unix.mkdir
Wrapper for Unix.rmdir
Wrapper for Unix.chdir
Wrapper for Unix.getcwd
Wrapper for Unix.chroot
Opens a directory for listing. Directories opened with this function must be explicitly closed with closedir. This is a cooperative analog of Unix.opendir.
Reads the next directory entry from the given directory. Special entries such as . and .. are included. If all entries have been read, raises End_of_file. This is a cooperative analog of Unix.readdir.
readdir_n handle count reads at most count entries from the given directory. It is more efficient than calling readdir count times. If the length of the returned array is smaller than count, this means that the end of the directory has been reached.
Resets the given directory handle, so that directory listing can be restarted. Cooperative analog of Unix.rewinddir.
Closes a directory handle. Cooperative analog of Unix.closedir.
files_of_directory dir returns the stream of all files of dir.
Pipes and redirections
pipe () creates pipe using Unix.pipe and returns two lwt file descriptors created from unix file_descriptor
pipe_in () is the same as pipe but maps only the unix file descriptor for reading into a lwt one. The second is not put into non-blocking mode. You usually want to use this before forking to receive data from the child process.
pipe_out () is the inverse of pipe_in. You usually want to use this before forking to send data to the child process
Wrapper for Unix.mkfifo
Symbolic links
Wrapper for Unix.symlink
Wrapper for Unix.readlink
Locking
Wrapper for Unix.lockf
User id, group id
type passwd_entry = Unix.passwd_entry = {pw_name : string;pw_passwd : string;pw_uid : int;pw_gid : int;pw_gecos : string;pw_dir : string;pw_shell : string;
}Wrapper for Unix.getlogin
Wrapper for Unix.getpwnam
Wrapper for Unix.getgrnam
Wrapper for Unix.getpwuid
Wrapper for Unix.getgrgid
Signals
Id of a signal handler, used to cancel it
on_signal signum f calls f each time the signal with numnber signum is received by the process. It returns a signal handler identifier that can be used to stop monitoring signum.
on_signal_full f is the same as on_signal f except that f also receive the signal handler identifier as argument so it can disable it.
Stops receiving this signal
Returns the number of registered signal handler.
reinstall_signal_handler signum if any signal handler is registered for this signal with on_signal, it reinstall the signal handler (with Sys.set_signal). This is useful in case another part of the program install another signal handler.
Sockets
socket domain type proto is the same as Unix.socket but maps the result into a lwt file descriptor
val socketpair :
?cloexec:bool ->
socket_domain ->
socket_type ->
int ->
file_descr * file_descrWrapper for Unix.socketpair
Wrapper for Unix.listen
Wrapper for Unix.accept
val accept_n :
?cloexec:bool ->
file_descr ->
int ->
((file_descr * sockaddr) list * exn option) Lwt.taccept_n fd count accepts up to count connections at one time.
- if no connection is available right now, it returns a pending promise
- if more than 1 and less than
countare available, it returns all of them
- if more than
countare available, it returns the nextcountof them
- if an error happens, it returns the connections that have been successfully accepted so far and the error
accept_n has the advantage of improving performance. If you want a more detailed description, you can have a look at:
Wrapper for Unix.connect
Wrapper for Unix.shutdown
Wrapper for Unix.getsockname
Wrapper for Unix.getpeername
Wrapper for Unix.recv.
On Windows, recv writes data into a temporary buffer, then copies it into the given one.
Wrapper for Unix.recvfrom.
On Windows, recvfrom writes data into a temporary buffer, then copies it into the given one.
Wrapper for Unix.send.
On Windows, send copies the given buffer before writing.
Wrapper for Unix.sendto.
On Windows, sendto copies the given buffer before writing.
val recv_msg :
socket:file_descr ->
io_vectors:IO_vectors.t ->
(int * Unix.file_descr list) Lwt.trecv_msg ~socket ~io_vectors receives data into a list of io-vectors, plus any file-descriptors that may accompany the messages. It returns a tuple whose first field is the number of bytes received and second is a list of received file descriptors. The messages themselves will be recorded in the provided io_vectors list. Data is written directly into the iov_buffer buffers.
Not implemented on Windows.
val send_msg :
socket:file_descr ->
io_vectors:IO_vectors.t ->
fds:Unix.file_descr list ->
int Lwt.tsend_msg ~socket ~io_vectors ~fds sends data from a list of io-vectors, accompanied with a list of file-descriptors. It returns the number of bytes sent. If fd-passing is not possible on the current system and fds is not empty, it raises Lwt_sys.Not_available "fd_passing". Data is written directly from the io_vectors buffers.
Not implemented on Windows.
val send_msgto :
socket:file_descr ->
io_vectors:IO_vectors.t ->
fds:Unix.file_descr list ->
dest:Unix.sockaddr ->
int Lwt.tsend_msgto ~socket ~io_vectors ~fds ~dest is similar to send_msg but takes an additional dest argument to set the address when using a connection-less socket.
Not implemented on Windows.
get_credentials fd returns credentials information from the given socket. On some platforms, obtaining the peer pid is not possible and it will be set to -1. If obtaining credentials is not possible on the current system, it raises Lwt_sys.Not_available "get_credentials".
This call is not available on windows.
Socket options
type socket_float_option = Unix.socket_float_option = | SO_RCVTIMEO| SO_SNDTIMEO(*Note: these options are provided for the sake of completeness only. Lwt places all sockets in non-blocking mode, for which these options are meaningless. Use
*)Lwt.pickwithLwt_unix.sleeporLwt_unix.timeoutfor timeouts.
Wrapper for Unix.getsockopt
Wrapper for Unix.setsockopt
Wrapper for Unix.getsockopt_int
Wrapper for Unix.setsockopt_int
Wrapper for Unix.getsockopt_optint
Wrapper for Unix.setsockopt_optint
Wrapper for Unix.getsockopt_float
Wrapper for Unix.setsockopt_float
Wrapper for Unix.getsockopt_error
Multicast functions
Whether sent multicast messages are received by the sending host
Set TTL/hops value
mcast_add_membership fd ~ifname addr joins the multicast group addr on the network interface ifname.
mcast_drop_membership fd ~ifname addr leaves the multicast group addr on the network interface ifname.
Host and protocol databases
type host_entry = Unix.host_entry = {h_name : string;h_aliases : string array;h_addrtype : socket_domain;h_addr_list : inet_addr array;
}Wrapper for Unix.gethostname
Wrapper for Unix.gethostbyname
Wrapper for Unix.gethostbyaddr
Wrapper for Unix.getprotobyname
Wrapper for Unix.getprotobynumber
Wrapper for Unix.getservbyname
Wrapper for Unix.getservbyport
type addr_info = Unix.addr_info = {ai_family : socket_domain;ai_socktype : socket_type;ai_protocol : int;ai_addr : sockaddr;ai_canonname : string;
}type getaddrinfo_option = Unix.getaddrinfo_option = | AI_FAMILY of socket_domain| AI_SOCKTYPE of socket_type| AI_PROTOCOL of int| AI_NUMERICHOST| AI_CANONNAME| AI_PASSIVE
Wrapper for Unix.getaddrinfo
Wrapper for Unix.getnameinfo
Terminal interface
type terminal_io = Unix.terminal_io = {mutable c_ignbrk : bool;mutable c_brkint : bool;mutable c_ignpar : bool;mutable c_parmrk : bool;mutable c_inpck : bool;mutable c_istrip : bool;mutable c_inlcr : bool;mutable c_igncr : bool;mutable c_icrnl : bool;mutable c_ixon : bool;mutable c_ixoff : bool;mutable c_opost : bool;mutable c_obaud : int;mutable c_ibaud : int;mutable c_csize : int;mutable c_cstopb : int;mutable c_cread : bool;mutable c_parenb : bool;mutable c_parodd : bool;mutable c_hupcl : bool;mutable c_clocal : bool;mutable c_isig : bool;mutable c_icanon : bool;mutable c_noflsh : bool;mutable c_echo : bool;mutable c_echoe : bool;mutable c_echok : bool;mutable c_echonl : bool;mutable c_vintr : char;mutable c_vquit : char;mutable c_verase : char;mutable c_vkill : char;mutable c_veof : char;mutable c_veol : char;mutable c_vmin : int;mutable c_vtime : int;mutable c_vstart : char;mutable c_vstop : char;
}Wrapper for Unix.tcgetattr
Wrapper for Unix.tcsetattr
Wrapper for Unix.tcsendbreak
Wrapper for Unix.tcdrain
Wrapper for Unix.tcflush
Wrapper for Unix.tcflow
Configuration (deprecated)
For system calls that cannot be made asynchronously, Lwt uses one of the following method:
Returns the default async method.
This can be initialized using the environment variable "LWT_ASYNC_METHOD" with possible values "none", "detach" and "switch".
Sets the default async method.
async_method () returns the async method used in the current thread.
The key for storing the local async method.
with_async_none f is a shorthand for:
Lwt.with_value async_method_key (Some Async_none) fwith_async_detach f is a shorthand for:
Lwt.with_value async_method_key (Some Async_detach) fwith_async_switch f is a shorthand for:
Lwt.with_value async_method_key (Some Async_switch) fLow-level interaction
If an action raises Retry, it will be requeued until the file descriptor becomes readable/writable again.
If an action raises Retry_read, it will be requeued until the file descriptor becomes readable.
If an action raises Retry_read, it will be requeued until the file descriptor becomes writables.
wrap_syscall set fd action wrap an action on a file descriptor. It tries to execute action, and if it can not be performed immediately without blocking, it is registered for later.
In the latter case, if the promise is canceled, action is removed from set.
check_descriptor fd raise an exception if fd is not in the state Open.
register_action set fd action registers action on fd. When fd becomes readable/writable action is called.
Note:
- you must call
check_descriptor fdbefore callingregister_action
- you should prefer using
wrap_syscall
Type of job descriptions. A job description describe how to call a C function and how to get its result. The C function may be executed in another system thread.
run_job ?async_method job starts job and wait for its termination.
The ~async_method argument will be ignored in Lwt 5.0.0, and this function will always act as if ~async_method:Async_detach is passed.
The async method is chosen follow:
- if the optional parameter
async_methodis specified, it is used, - otherwise if the local key
async_method_keyis set in the current thread, it is used, - otherwise the default method (returned by
default_async_method) is used.
If the method is Async_none then the job is run synchronously and may block the current system thread, thus blocking all Lwt threads.
If the method is Async_detach then the job is run in another system thread, unless the the maximum number of worker threads has been reached (as given by pool_size).
If the method is Async_switch then the job is run synchronously and if it blocks, execution will continue in another system thread (unless the limit is reached).
abort_jobs exn make all pending jobs to fail with exn. Note that this does not abort the real job (i.e. the C function executing it), just the lwt thread for it.
cancel_jobs () is the same as abort_jobs Lwt.Canceled.
val execute_job :
?async_method:async_method ->
job:'a job ->
result:('a job -> 'b) ->
free:('a job -> unit) ->
'b Lwt.tNotifications
Lwt internally use a pipe to send notification to the main thread. The following functions allow to use this pipe.
make_notification ?once f registers a new notifier. It returns the id of the notifier. Each time a notification with this id is received, f is called.
if once is specified, then the notification is stopped after the first time it is received. It defaults to false.
send_notification id sends a notification.
This function is thread-safe.
Stop the given notification. Note that you should not reuse the id after the notification has been stopped, the result is unspecified if you do so.
Call the handler associated to the given notification. Note that if the notification was defined with once = true it is removed.
set_notification id f replace the function associated to the notification by f. It raises Not_found if the given notification is not found.
System threads pool
If the program is using the async method Async_detach or Async_switch, Lwt will launch system threads to execute blocking system calls asynchronously.
Maximum number of system threads that can be started. If this limit is reached, jobs will be executed synchronously.
Change the size of the pool.
The number of system threads running (excluding this one).
The number threads waiting for a job.
CPUs
get_cpu () returns the number of the CPU the current thread is running on.
get_affinity ?pid () returns the list of CPUs the process with pid pid is allowed to run on. If pid is not specified then the affinity of the current process is returned.
set_affinity ?pid cpus sets the list of CPUs the given process is allowed to run on.
Versioned interfaces
- Sleeping
- Operations on file-descriptors
- Process handling
- Basic file input/output
- Seeking and truncating
- Syncing
- File status
- File operations on large files
- Operations on file names
- File permissions and ownership
- Operations on file descriptors
- Directories
- Pipes and redirections
- Symbolic links
- Locking
- User id, group id
- Signals
- Sockets
- Host and protocol databases
- Terminal interface
- Configuration (deprecated)
- Low-level interaction
- Notifications
- System threads pool
- CPUs
- Versioned interfaces