std::filesystem::is_socket (3) - Linux Manuals
std::filesystem::is_socket: std::filesystem::is_socket
NAME
std::filesystem::is_socket - std::filesystem::is_socket
Synopsis
Defined in header <filesystem>
bool is_socket( std::filesystem::file_status s ) noexcept; (1) (since C++17)
bool is_socket( const std::filesystem::path& p ); (2) (since C++17)
bool is_socket( const std::filesystem::path& p, std::error_code& ec ) noexcept;
Checks if the given file status or path corresponds to a named IPC socket, as if determined by the POSIX S_IFSOCK.
1) Equivalent to s.type() == file_type::socket.
2) Equivalent to is_socket(status(p)) or is_socket(status(p, ec)).
Parameters
s - file status to check
p - path to examine
ec - out-parameter for error reporting in the non-throwing overload
Return value
true if the file indicated by p or if the type indicated s refers to a named socket. The non-throwing overload returns false if an error occurs.
Exceptions
2) The overload that does not take a std::error_code& parameter throws filesystem_error on underlying OS API errors, constructed with p as the first path argument and the OS error code as the error code argument. The overload taking a std::error_code& parameter sets it to the OS API error code if an OS API call fails, and executes ec.clear() if no errors occur. Any overload not marked noexcept may throw std::bad_alloc if memory allocation fails.
Notes
Named sockets are UNIX domain sockets constructed with socket and bind POSIX APIs, which may be used for advanced interprocess communication. In particular, they may be used to transport open file descriptors from one running process to another.
Example
// Run this code
Possible output:
See also
status determines file attributes
symlink_status determines file attributes, checking the symlink target
(C++17)
(C++17)
file_status represents file type and permissions
(C++17)
status_known checks whether file status is known
(C++17)
is_block_file checks whether the given path refers to block device