RESOLVEPATH(3)

💅 RESOLVEPATH(3) — Schily's LIBRARY FUNCTIONS 🌸

okay bestie, gather round, because this one's from Schily's LIBRARY FUNCTIONS and it's literally the glow-up your path names have been waiting for 💖

---

✨ NAME ✨

resolvepath(), resolvenpath(), resolvefpath() — resolve all symbolic links of a path name 🦋

No cap, that's the whole vibe: you hand it a path, it hands you back a path with zero symlinks in it. Iconic.

---

🎀 SYNOPSIS 🎀

#include <schily/schily.h>

int
resolvepath(path, buf, bufsiz)
        const char    *path;
              char    *buf;
              size_t  bufsiz;

int
resolvenpath(path, buf, bufsiz)
        const char    *path;
              char    *buf;
              size_t  bufsiz;

int
resolvefpath(path, buf, bufsiz, flags)
        const char    *path;
              char    *buf;
              size_t  bufsiz;
              int     flags;

look at that alignment, whoever formatted this ate 💅

---

🌈 DESCRIPTION 🌈

so resolvepath() takes a relative path name and resolves all symbolic links in the path name. The result is a path name that is free of symbolic links — literally symlink-free, a clean slate, main character energy ✨

• path — a relative path name that is used as the input 🫶
• buf — the buffer used for the result of the conversion 💖
• bufsiz — the size of the result buffer 🎀

All ''.'' components are eliminated, and every non-leading ''..'' component is eliminated together with its preceding directory component. If leading ''..'' components reach to the root directory, they are replaced by ''/''. periodt — the .. drama gets cancelled out 💀

resolvenpath() behaves like resolvepath() except that the file does not need to exist. ghosting the filesystem, honestly 👻

resolvefpath() takes an additional flags parameter from the set of flags from the following set:

• RSPF_EXIST — all path components must exist 👑
• RSPF_NOFOLLOW_LAST — don't follow symbolic links in the last path component 🙈

---

💜 RETURN VALUE 💜

Upon successful completion, resolvepath(), resolvenpath() and resolvefpath() return the number of bytes placed in the buffer. Slay 💅

Otherwise, -1 is returned and errno is set to indicate the error. And in case of an error, the contents of the result buffer is left in an intermediate state — so like, don't trust what's in there, it's giving half-finished group project 😭

---

🔥 ERRORS 🔥

• ERANGE — the path does not fit into the suplied buffer.
• EFAULT — a null pointer was suplied as pathname.
• EINVAL — an empty relative path was supplied.
• other — any other value that may be a result of an underlying filesystem operation.

(and yes bestie the typos are in the original, I'm not fixing them, that's not my job ✨)

---

⭐ USAGE ⭐

Applications should not assume that the returned contents of the buffer are null-terminated. This is because the function resolvepath(3) may be the Solaris version if the program is compiled on Solaris. 🫠

ngl that's the kind of ✨platform surprise✨ that ruins your whole afternoon, so just... don't assume. check bufsiz, live your truth, be free 🦋

---

🧚 SEE ALSO 🧚

• resolvepath(3)
• resolvenpath(3)
• resolvefpath(3)

yes, it's citing itself, we love a self-aware icon 🙈

---

💀 NOTES 💀

none

that's it. that's the note. short and iconic, honestly 👑

---

anyway that's the whole page, bestie — go forth and resolve those paths, you're gonna do amazing 🎀

this masterpiece was brought to you by Joerg Schilling, dated 2022/09/09, in the year of our lord 🌸 stay hydrated, back up your buffers, and remember: no cap, always check that return value 💖✨🦋