|
NAMEexplain_setsockopt - explain setsockopt(2) errorsSYNOPSIS#include <libexplain/setsockopt.h>const char *explain_setsockopt(int fildes, int level, int name,
void *data, socklen_t data_size);
DESCRIPTIONThese functions may be used to obtain explanations for errors returned by the setsockopt(2) system call.explain_setsockoptconst char *explain_setsockopt(int fildes, int level, int name, void *data, socklen_t data_size);The explain_setsockopt function is used to obtain an explanation of an error returned by the setsockopt(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. This function is intended to be used in a fashion similar to the following example: if (setsockopt(fildes, level, name, data, data_size) < 0) { fprintf(stderr, "%s\n", explain_setsockopt(fildes, level, name, data, data_size)); exit(EXIT_FAILURE); } The above code example is available pre‐packaged as the explain_setsockopt_or_die(3) function.
Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_errno_setsockoptconst char *explain_errno_setsockopt(int errnum, int fildes, int level, int name, void *data, socklen_t data_size);The explain_errno_setsockopt function is used to obtain an explanation of an error returned by the setsockopt(2) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (setsockopt(fildes, level, name, data, data_size) < 0) { int err = errno; fprintf(stderr, "%s\n", explain_errno_setsockopt(err, fildes, level, name, data, data_size)); exit(EXIT_FAILURE); } The above code example is available pre‐packaged as the explain_setsockopt_or_die(3) function.
Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_message_setsockoptvoid explain_message_setsockopt(char *message, int message_size, int fildes, int level, int name, void *data, socklen_t data_size);The explain_message_setsockopt function may be used to obtain an explanation of an error returned by the setsockopt(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. This function is intended to be used in a fashion similar to the following example: if (setsockopt(fildes, level, name, data, data_size) < 0) { char message[3000]; explain_message_setsockopt(message, sizeof(message), fildes, level, name, data, data_size); fprintf(stderr, "%s\n", message); exit(EXIT_FAILURE); } The above code example is available pre‐packaged as the explain_setsockopt_or_die(3) function.
explain_message_errno_setsockoptvoid explain_message_errno_setsockopt(char *message, int message_size, int errnum, int fildes, int level, int name, void *data, socklen_t data_size);The explain_message_errno_setsockopt function may be used to obtain an explanation of an error returned by the setsockopt(2) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (setsockopt(fildes, level, name, data, data_size) < 0) { int err = errno; char message[3000]; explain_message_errno_setsockopt(message, sizeof(message), err, fildes, level, name, data, data_size); fprintf(stderr, "%s\n", message); exit(EXIT_FAILURE); } The above code example is available pre‐packaged as the explain_setsockopt_or_die(3) function.
SEE ALSO
COPYRIGHTlibexplain version 1.3Copyright (C) 2009 Peter Miller Visit the GSP FreeBSD Man Page Interface. |