PTS_SOURCE(1)

💖 pts_source — bestie, it's manual page o'clock 💖

okay so this is pts_source(1) straight outta the AFS Command Reference, and no cap, it's a lil cutie. Sit down, grab a strawberry 🍓, and let's get you fluent.

---

✨ NAME ✨

pts_source — read pts commands from a file 📄✨

---

🌸 SYNOPSIS 🌸

Here's the whole vibe, both spellings, all the flags, zero skips:

pts source [-file] <file name> [-cell] <cell name>
   [-noauth] [-localauth] [-force] [-auth] [-encrypt] [-help]
   [-config <config directory>]

pts so [-f] <file name> [-c] <cell name>
   [-n] [-l] [-f] [-h] [-a] [-e] [-co <config directory>]

(yes -f shows up twice in the short version, once for -file and once for -force. that's not a typo, that's just the era it was written in 💀)

---

🦋 DESCRIPTION 🦋

pts source runs the commands sitting inside a file as if you had literally typed them into pts interactive mode. That's it, that's the whole plot. You can call it from the command line, or you can call it from inside an interactive session — both work, both slay. 💅

---

💀 CAUTIONS 💀

Drama alert, history lesson time. Before OpenAFS 1.4.5 and OpenAFS 1.5.23, pts source was only available on Unix or Linux, and only if OpenAFS had been compiled with the supergroups option — which, btw, is disabled by default. As of OpenAFS 1.4.5 and 1.5.23? It's always available. No more gatekeeping, we love to see it. ✨

---

👑 OPTIONS 👑

pts source takes the following options, and bestie, here's every single one:

• -file <file name> — tells it which file to read commands from. Everything in that file runs exactly as if you'd typed it into pts interactive mode. 🎀
• -auth — use the calling user's tokens to talk to the Protection Server. More deets? That's pts(1), go look. 🫶
• -cell <cell name> — names the cell you wanna run the command in. Again, more deets in pts(1).
• -config <config directory> — use an alternate config directory. Yep, more deets in pts(1). 😭
• -encrypt — encrypts any communication with the Protection Server. You already know where the deets are: pts(1).
• -force — the "keep going, bestie" flag. It lets the command push through as far as it possibly can when errors or other problems happen, instead of slamming the brakes at the very first error. 🔥
• -help — prints the online help for this command. And heads up, all other valid options get ignored when you use this one. 🙈
• -localauth — constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. Do not combine this flag with -cell or -noauth. For more details, pts(1).
• -noauth — assigns the unprivileged identity anonymous to the issuer. For more details, pts(1).

---

🌈 OUTPUT 🌈

It shows you the output of every command in the file, as if each one had been run normally. No mystery, no filter, just the receipts. 💅

---

🌟 EXAMPLES 🌟

Here's pts source doing its thing inside a pts interactive session:

% echo examine admin > /tmp/commands.txt
% pts interactive
pts> source /tmp/commands.txt
Name: admin, id: 1, owner: system:administrators, creator: anonymous,
  membership: 2, flags: S----, group quota: 20.
pts> quit
%

iconic. ate. periodt. 👑

---

💜 SEE ALSO 💜

pts(1), pts_interactive(1), pts_quit(1), pts_sleep(1)

---

🎀 COPYRIGHT 🎀

Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>

This documentation is covered by the BSD License as written in the doc/LICENSE file. This man page was written by Jason Edgecombe for OpenAFS.

---

okay that's the whole page, you're officially fluent in pts source now 🧚✨ This lil bop comes to you from OpenAFS, dated 2026-07-27, filed under PTS_SOURCE(1) — and that's a wrap, bestie, go run those commands 💖🦋🌸