PVFS2-CHMOD(1)
π pvfs2-chmod β the girlies' guide to OrangeFS permissions
okay so bestie, welcome to pvfs2-chmod(1), a page from the General Commands Manual section. It's giving "I just want to fix my file perms" energy and honestly? Same. Let's go. β¨
πΈ NAME πΈ
pvfs2-chmod β modify permissions on files in OrangeFS volumes. That's it, that's the whole job, and it does it flawlessly. π
π SYNOPSIS π
pvfs2-chmod [-v] mode filename(s)
yeah it's short. it's iconic. it doesn't need to be long. periodt.
β¨ DESCRIPTION β¨
So like, the pvfs2-chmod utility modifies the permission bits on the OrangeFS files you point it at. π«
And the mode? You write it as a three or four digit octal number, in the conventional manner. That's the whole vibe β digits, not letters. (More on that in CAVEATS, bestie, and you're gonna want to read it fr fr. π)
The options are as follows:
-vβ print the version number and exit. That's literally all it does. Cute, quick, slay. π«Ά
π ENVIRONMENT π
Environment variables, aka the settings that be lurking in the background:
PVFS2_DEBUGFILEβ if you set this to the path of a local file, the debug output gets redirected to it. All the messy little thoughts go in the file instead of your terminal. πPVFS2_DEBUGMASKβ sets the OrangeFS debug mask. The possible masks are documented over inpvfs2-set-debugmask(1), so go read that one if you're nosy. πPVFS2TAB_FILEβ if it's set, it's the full pathname for an alternatepvfs2tabfile. An alternate. Fancy. π
π FILES π
/etc/pvfs2tab
one file. one legend. π
π₯ EXAMPLES π₯
Prevent other users from accessing a file. No one else gets in, we're gatekeeping:
pvfs2-chmod 600 /mnt/foo
Allow the owner and users in the file's group to read and modify the file, and other users to only read the file. So: owner + group get read and modify, everyone else just gets read:
pvfs2-chmod 664 /mnt/foo
see how the mode is literally just the octal digits and the path? no dashes, no u+x, just numbers and vibes. π
π CAVEATS π
okay this is the important part, do not scroll past this.
- This utility does not support symbolic permissions like the
chmod(1)utility does. So nou+rwx, nogo-w, none of that. Octal only. It's a choice, and it's the choice we live with. π - And ngl, here's the big one: because OrangeFS is a network file system, any user with access to the network may be able to circumvent file permissions. Yeah. Read that again. The permissions are cute but the network is not always your friend. Be aware. π
π BUGS π
Please submit bug reports to devel@lists.orangefs.org β the devs want to hear from you, bestie, don't be shy. π
π SEE ALSO π
go read those too, they're the friend group. π¦
and that's the page!! this one's from 2017-07-03, source/version and date both intact because we respect the archive in this house. mwah, go fix those perms, you ate. πβ¨π
π¦ where this page comes from
- fedora 44: orangefs 2.10.1-3.fc44 Β· LicenseRef-Callaway-LGPLv2+ AND LicenseRef-Callaway-LGPLv2 AND LicenseRef-Callaway-BSD AND LicenseRef-Callaway-MIT AND Zlib
- fedora 44: orangefs 2.10.1-3.fc44 Β· LicenseRef-Callaway-LGPLv2+ AND LicenseRef-Callaway-LGPLv2 AND LicenseRef-Callaway-BSD AND LicenseRef-Callaway-MIT AND Zlib
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms