PTS_LISTMAX(1)

πŸ’– PTS_LISTMAX β€” the AFS Command Reference glow-up edition πŸ’–

okay bestie, so this is pts_listmax(1) from the AFS Command Reference, and it's honestly the chillest little command in the whole pts family. no cap. it just tells you numbers. that's the whole gig. πŸŽ€


✨ NAME ✨

pts_listmax β€” displays the max user id and max group id counters πŸ¦‹


✨ SYNOPSIS ✨

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

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

✨ DESCRIPTION ✨

So pts listmax displays the values of the "max user id" and "max group id" counters. πŸ’…

And what are those, you ask? They're the little bookkeeping numbers the Protection Server uses to keep track of:

  • the AFS user IDs (AFS UIDs) it hands out to brand-new users or machines, and
  • the AFS group IDs (AFS GIDs) it hands out to brand-new groups.

respectively. yep. one counter each. iconic behavior honestly. ✨

Now here's the tea, and it's the important tea: when an administrator next issues the pts createuser command and does not include the -id argument, the new user or machine receives an AFS UID one greater than the "max user id" counter. and when a user issues the pts creategroup command and does not include the -id argument, the new group receives an AFS UID one less (more negative) than the "max group id" counter. 🌸

and if you wanna reset one or both of those counters? members of the system:administrators group can issue the pts setmax command. main character energy only, obviously. πŸ‘‘


✨ OPTIONS ✨

  • -auth β€” uses the calling user's tokens to talk to the Protection Server. more deets are in pts(1). 🫢
  • -cell <cell name> β€” names the cell where you wanna run the command. more deets in pts(1).
  • -config <config directory> β€” use an alternate config directory. more deets in pts(1). πŸŽ€
  • -encrypt β€” encrypts any communication with the Protection Server. more deets in pts(1). πŸ”
  • -force β€” lets the command keep going as far as it possibly can when errors or other problems pop up, instead of just halting at the first error. that girl does not give up. πŸ’ͺ
  • -help β€” prints the online help for this command. and fyi, all other valid options are ignored. it said what it said. πŸ’€
  • -localauth β€” constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. do not combine this flag with the -cell or -noauth options. like, seriously, don't. 🚫 more deets in pts(1).
  • -noauth β€” assigns the unprivileged identity anonymous to the issuer. more deets in pts(1). yes, you're nobody now. slay. πŸ™ˆ

✨ OUTPUT ✨

the command displays the counters in this exact format, and yes, we're keeping it exactly:

Max user id is <user_counter> and max group id is <group_counter>.

✨ EXAMPLES ✨

here's the example, displaying the output of this command:

% pts listmax
Max user name is 1271 and max group id is -382.
bestie I know, I know β€” the example says Max user name and not Max user id. that's what the original says, so that's what you get. I don't make the rules, I just vibe with 'em. 😭

✨ PRIVILEGE REQUIRED ✨

None. literally none. go off, you need zero clout for this one. πŸŽ‰


✨ SEE ALSO ✨


IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.


aaaand that's the whole page bestie πŸ’– this is OpenAFS, dated 2026-07-27 β€” go forth and pts listmax your little heart out. periodt. πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from