KPSEACCESS(1)

πŸ’– KPSEACCESS πŸ’–

okay bestie, welcome to the General Commands Manual glow-up of kpseaccess β€” literally the tiny little tool that answers one (1) question: can I touch this file or nah? πŸ”₯


🌸 NAME 🌸

kpseaccess β€” determine whether a file can be accessed πŸ’…


✨ SYNOPSIS ✨

kpseaccess mode file

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the vibe: kpseaccess exits successfully if file can be accessed with the mode you specified. That's it. That's the whole job. Iconic, honestly. πŸ‘‘

The mode is an optional dash (-) followed by zero or more letters from rwx, where:

  • r β€” for readable
  • w β€” for writable
  • x β€” for executable

yes bestie, zero or more β€” an empty letter list is valid, the dash is optional, we love a flexible queen πŸŽ€


πŸ’€ the plot twist: kpseaccess vs test

The difference between kpseaccess and test is that test looks at the permission bits, while kpseaccess checks using the access(2) system call. 🫢

and the way that matters?! it makes a difference when file systems have been mounted read-only. like, the bits might say one thing and the actual system call says another, and kpseaccess is the one asking the system directly. no cap. 😭


🌈 OPTIONS 🌈

kpseaccess accepts the following options:

  • --help β€” print help message and exit 🧚
  • --version β€” print version information and exit ⭐

πŸ“ SEE ALSO πŸ“


okay that's the whole page, you ate that πŸ’– the source of all this wisdom is Kpathsea 6.4.1, dated 1 March 2011 β€” yes she's an elder but she's still serving ✨ bye bestie, go check those files πŸ’…πŸŒΈ