explain_chroot(3)

💖 explain_chroot — bestie's guide to chroot(2) error lore 💖

ok so like. this is explain_chroot(3), from the Library Functions Manual, and she is serving explanations for your chroot(2) errors. no cap. 🎀

---

✨ NAME ✨

explain_chroot — explain chroot(2) errors. that's it, that's the whole job, and she does it gorgeously 💅

---

🦋 SYNOPSIS 🦋

#include <libexplain/chroot.h>
const char *explain_chroot(const char *pathname);
const char *explain_errno_chroot(int errnum, const char *pathname);
void explain_message_chroot(char *message, int message_size, const char
*pathname);
void explain_message_errno_chroot(char *message, int message_size, int
errnum, const char *pathname);

four functions, four vibes, all iconic 👑

---

🌸 DESCRIPTION 🌸

okay so here's the tea bestie: these functions may be used to obtain explanations for errors returned by the chroot(2) system call. that's the whole point. that's the mission. she ate 💖

---

🧚 explain_chroot

const char *explain_chroot(const char *pathname);

The explain_chroot function is used to obtain an explanation of an error returned by the chroot(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. like she's not gonna just say "something broke", she's gonna tell you why, periodt ✨

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

• pathname — The original pathname, exactly as passed to the chroot(2) system call. do not paraphrase her, she remembers everything fr fr 👀

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. so like... she's a communal queen, the buffer belongs to everyone, tread carefully 😭

Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. it's giving "everyone shares one lip gloss" energy. chaos. 💀

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

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

The above code example is available pre‐packaged as the explain_chroot_or_die(3) function. she comes ready-made bestie, no assembly required 🫶

---

🌈 explain_errno_chroot

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

The explain_errno_chroot function is used to obtain an explanation of an error returned by the chroot(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. so like, grab that errno early or the libc girlies will snatch it from you 💅
• pathname — The original pathname, exactly as passed to the chroot(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. highkey a red flag but she's still cute 😭

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

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

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

---

🎀 explain_message_chroot

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

The explain_message_chroot function is used to obtain an explanation of an error returned by the chroot(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. ohhh look at her, she fixed it, she's evolved, main character growth arc 👑
• message_size — The size in bytes of the location in which to store the returned message. count your bytes bestie, don't overflow 🌸
• pathname — The original pathname, exactly as passed to the chroot(2) system call.

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

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

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

---

🍓 explain_message_errno_chroot

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

The explain_message_errno_chroot function is used to obtain an explanation of an error returned by the chroot(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. the safe queen returns 🙈
• 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. yes we said this already but it matters okay 😤
• pathname — The original pathname, exactly as passed to the chroot(2) system call.

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

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

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

---

👀 SEE ALSO 👀

• chroot(2) — change root directory. the og. the blueprint. the moment. 🔥
• explain_chroot_or_die(3) — change root directory and report errors. the pre-packaged version, for when you want the explanation and the dramatic exit 💀

---

💜 COPYRIGHT 💜

libexplain version 1.4 Copyright (C) 2009 Peter Miller

---

okay bestie that's the whole page, you're literally a chroot(2) error-decoding icon now, go forth and fprintf(stderr, ...) with confidence 💖✨🎀🦋🌸💅🫶

explain_chroot(3) — Library Functions Manual — out 💅