VOP_PATHCONF(9)

💖 VOP_PATHCONF 💖

okay bestie, so this is a page from the Kernel Developer's Manual — section 9, kernel-adjacent, very much for the devs poking around in the vnode layer 👑 — and it's called VOP_PATHCONF. Sit down, grab a boba, we're getting into it. 🧋✨

✨ NAME ✨

VOP_PATHCONF — return POSIX pathconf information

🌸 SYNOPSIS 🌸

#include <sys/param.h>
#include <sys/vnode.h>
#include <sys/unistd.h>

int
VOP_PATHCONF(struct vnode *vp, int name, long *retval);

🦋 DESCRIPTION 🦋

So basically, the arguments are giving:

• vp — the vnode we wanna get info about 👀
• name — the type of information to return, like the category, the vibe of the question
• retval — the place to return the information, i.e. where the answer gets dropped off 🎁

And the value of name is literally what decides what comes back:

• _PC_LINK_MAX — the maximum number of links to a file 🔗
• _PC_NAME_MAX — the maximum number of bytes in a file name 📛
• _PC_PATH_MAX — the maximum number of bytes in a pathname 🛤️
• _PC_PIPE_BUF — the maximum number of bytes which will be written atomically to a pipe 🚰
• _PC_CHOWN_RESTRICTED — returns 1 if appropriate privileges are required for the chown(2) system call, otherwise 0 🔐
• _PC_NO_TRUNC — returns 1 if file names longer than KERN_NAME_MAX are truncated ✂️

💅 RETURN VALUES 💅

If name is recognized, *retval gets set to the specified value and zero is returned. If it's not recognized? EINVAL. no in-between, that's just how she goes 😌

🎀 SEE ALSO 🎀

• pathconf(2)
• vnode(9)

👑 AUTHORS 👑

This manual page was written by Doug Rabson. iconic of him, honestly 🫶

okay that's the whole thing, you ate that, go forth and pathconf responsibly 💜

Debian • July 21, 2019 — that's the version-and-date sign-off bestie, mwah 💋✨