explain_accept4

The explain_accept4 function is used to obtain an explanation of an error returned by the accept4(2) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail.

The errno global variable will be used to obtain the error value to be decoded.

fildes

The original fildes, exactly as passed to the accept4(2) system call.

sock_addr

The original sock_addr, exactly as passed to the accept4(2) system call.

sock_addr_size

The original sock_addr_size, exactly as passed to the accept4(2) system call.

flags

The original flags, exactly as passed to the accept4(2) system call.

Returns:

The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads.

Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library.

Example: This function is intended to be used in a fashion similar to the following example:

{

    exit(EXIT_FAILURE);
}

The above code example is available pre‐packaged as the explain_accept4_or_die(3) function.

explain_errno_accept4

The explain_errno_accept4 function is used to obtain an explanation of an error returned by the accept4(2) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail.

errnum

The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is necessary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno.

fildes

The original fildes, exactly as passed to the accept4(2) system call.

sock_addr

The original sock_addr, exactly as passed to the accept4(2) system call.

sock_addr_size

The original sock_addr_size, exactly as passed to the accept4(2) system call.

flags

The original flags, exactly as passed to the accept4(2) system call.

Returns:

The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads.

Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library.

Example: This function is intended to be used in a fashion similar to the following example:

{
    int err = errno;

    exit(EXIT_FAILURE);
}

The above code example is available pre‐packaged as the explain_accept4_or_die(3) function.

explain_message_accept4

The explain_message_accept4 function is used to obtain an explanation of an error returned by the accept4(2) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail.

The errno global variable will be used to obtain the error value to be decoded.

message

The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe.

message_size

The size in bytes of the location in which to store the returned message.

fildes

The original fildes, exactly as passed to the accept4(2) system call.

sock_addr

The original sock_addr, exactly as passed to the accept4(2) system call.

sock_addr_size

The original sock_addr_size, exactly as passed to the accept4(2) system call.

flags

The original flags, exactly as passed to the accept4(2) system call.

Example: This function is intended to be used in a fashion similar to the following example:

{
    char message[3000];

    fprintf(stderr, "%s\n", message);
    exit(EXIT_FAILURE);
}

The above code example is available pre‐packaged as the explain_accept4_or_die(3) function.

explain_message_errno_accept4

The explain_message_errno_accept4 function is used to obtain an explanation of an error returned by the accept4(2) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail.

message

The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe.

message_size

The size in bytes of the location in which to store the returned message.

errnum

The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is necessary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno.

fildes

The original fildes, exactly as passed to the accept4(2) system call.

sock_addr

The original sock_addr, exactly as passed to the accept4(2) system call.

sock_addr_size

The original sock_addr_size, exactly as passed to the accept4(2) system call.

flags

The original flags, exactly as passed to the accept4(2) system call.

Example: This function is intended to be used in a fashion similar to the following example:

{
    int err = errno;
    char message[3000];

    fprintf(stderr, "%s\n", message);
    exit(EXIT_FAILURE);
}

The above code example is available pre‐packaged as the explain_accept4_or_die(3) function.