DOKK / manpages / debian 10 / libexplain-dev / explain_unlink.3.en
explain_unlink(3) Library Functions Manual explain_unlink(3)

explain_unlink - explain unlink(2) errors

#include <libexplain/unlink.h>
const char *explain_unlink(const char *pathname);
void explain_message_unlink(char *message, int message_size, const char *pathname);
const char *explain_errno_unlink(int errnum, const char *pathname);
void explain_message_errno_unlink(char *message, int message_size, int errnum, const char *pathname);

These functions may be used to obtain explanations for unlink(2) errors.

const char *explain_unlink(const char *pathname);

The explain_unlink function is used to obtain an explanation of an error returned by the unlink(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 (unlink(pathname) < 0)
{

fprintf(stderr, '%s0, explain_unlink(pathname));
exit(EXIT_FAILURE); }
The original pathname, exactly as passed to the unlink(2) system call.
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.

const char *explain_errno_unlink(int errnum, const char * pathname);

The explain_errno_unlink function is used to obtain an explanation of an error returned by the unlink(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 (unlink(pathname) < 0)
{

int err = errno;
fprintf(stderr, '%s0, explain_errno_unlink(err, pathname));
exit(EXIT_FAILURE); }
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.
The original pathname, exactly as passed to the unlink(2) system call.
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.

void explain_message_unlink(char *message, int message_size, const char *pathname);

The explain_message_unlink function is used to obtain an explanation of an error returned by the unlink(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 (unlink(pathname) < 0)
{

char message[3000];
explain_message_unlink(message, sizeof(message), pathname);
fprintf(stderr, '%s0, message);
exit(EXIT_FAILURE); }
The location in which to store the returned message. Because a message return buffer has been supplied, this function is thread safe.
The size in bytes of the location in which to store the returned message.
The original pathname, exactly as passed to the unlink(2) system call.

void explain_message_errno_unlink(char *message, int message_size, int errnum, const char *pathname);

The explain_message_errno_unlink function is used to obtain an explanation of an error returned by the unlink(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 (unlink(pathname) < 0)
{

int err = errno;
char message[3000];
explain_message_errno_unlink(message, sizeof(message), err,
pathname);
fprintf(stderr, '%s0, message);
exit(EXIT_FAILURE); }
The location in which to store the returned message. Because a message return buffer has been supplied, this function is thread safe.
The size in bytes of the location in which to store the returned message.
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.
The original pathname, exactly as passed to the unlink(2) system call.

libexplain version 1.4
Copyright (C) 2008 Peter Miller

Written by Peter Miller <pmiller@opensource.org.au>