explain_acct(3)

💖 explain_acct(3) — the libexplain girlies' guide 💖

okay bestie, so this is a page from the Library Functions Manual, and it's all about the explain_acct(3) squad — four lil functions whose whole job is to tell you why acct(2) said no. no cap. 🫶

---

✨ NAME ✨

explain_acct — explain acct(2) errors 🎀

---

🌸 SYNOPSIS 🌸

#include <libexplain/acct.h>
const char *explain_acct(const char *pathname);
const char *explain_errno_acct(int errnum, const char *pathname);
void explain_message_acct(char *message, int message_size, const char *pathname);
void explain_message_errno_acct(char *message, int message_size, int errnum, const char *pathname);

---

💅 DESCRIPTION 💅

these functions are literally here to hand you explanations for errors that the acct(2) system call throws back at you. it's giving "let me translate the cryptic vibes for you". 🌈

🦋 explain_acct 🦋

const char *explain_acct(const char *pathname);

explain_acct is the one you call when you want the tea on an error returned by the acct(2) system call. the least it's ever gonna give you is the value of strerror(errno) — but usually it pops off way harder than that and points at the actual underlying cause in more detail. periodt. 🔥

the errno global variable is what gets used to grab the error value that needs decoding.

• pathname — the original pathname, exactly as passed to the acct(2) system call. not a remix, not an edit, the literal same one. 💯

Returns: the message explaining the error. this message buffer is shared by all libexplain functions that don't supply a buffer in their argument list. it will be overwritten by the next call to any libexplain function that shares this buffer — including other threads. 😭 so yeah, screenshot it fast or copy it out.

Note: this function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library do the same. group chat rules: everyone's talking, only one buffer. 💀

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

if (acct(pathname) < 0)
{
    fprintf(stderr, "%s\n", explain_acct(pathname));
    exit(EXIT_FAILURE);
}

the above code example is available pre‐packaged as the explain_acct_or_die(3) function. it's already got its fit on, you just show up. ✨

🌟 explain_errno_acct 🌟

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

explain_errno_acct does the same thing — it hands you an explanation of an error returned by the acct(2) system call. the least the message will contain is the value of strerror(errno), but usually it does way better and clues you in on the underlying cause in more detail. 💜

• errnum — the error value to be decoded, usually grabbed from the errno global variable right before you call this function. this matters if you need to run any code between the system call being explained and this function, because a whole bunch of libc functions will mess with the value of errno behind your back. 🙈 grab it early, bestie.
• pathname — the original pathname, exactly as passed to the acct(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:

if (acct(pathname) < 0)
{
    int err = errno;
    fprintf(stderr, "%s\n", explain_errno_acct(err, pathname));
    exit(EXIT_FAILURE);
}

the above code example is available pre‐packaged as the explain_acct_or_die(3) function. 🎀

🌈 explain_message_acct 🌈

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

explain_message_acct gets you an explanation of an error returned by the acct(2) system call. the least the message will contain is the value of strerror(errno), but usually it does much better and indicates the underlying cause in more detail. slay. 💅

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 you supply a suitable message return buffer, this function is thread safe. look at her go. 🦋
• message_size — the size in bytes of the location in which to store the returned message.
• pathname — the original pathname, exactly as passed to the acct(2) system call.

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

if (acct(pathname) < 0)
{
    char message[3000];
    explain_message_acct(message, sizeof(message), pathname);
    fprintf(stderr, "%s\n", message);
    exit(EXIT_FAILURE);
}

the above code example is available pre‐packaged as the explain_acct_or_die(3) function. ⭐

🧚 explain_message_errno_acct 🧚

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

explain_message_errno_acct is the final boss of explanations for errors returned by the acct(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. no notes. 💯

• 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. (they're messy like that. 😭)
• pathname — the original pathname, exactly as passed to the acct(2) system call.

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

if (acct(pathname) < 0)
{
    int err = errno;
    char message[3000];
    explain_message_errno_acct(message, sizeof(message), err,
    pathname);
    fprintf(stderr, "%s\n", message);
    exit(EXIT_FAILURE);
}

the above code example is available pre‐packaged as the explain_acct_or_die(3) function. 👑

---

🔥 SEE ALSO 🔥

• acct(2) — switch process accounting on or off
• explain_acct_or_die(3) — switch process accounting on or off and report errors

---

💜 COPYRIGHT 💜

libexplain version 1.4 Copyright (C) 2009 Peter Miller

---

and that's the whole page, bestie 🎀 shoutout to libexplain version 1.4 and Copyright (C) 2009 Peter Miller for making it happen — now go forth and explain those acct(2) errors like the main character you are. mwah. 💋✨