XSTAT_CM_TEST(1)

πŸ’– XSTAT_CM_TEST πŸ’–

okay so real talk bestie, this is the man page for xstat_cm_test from the AFS Command Reference β€” it's a command reference page, so buckle up, we're going full technical and I'm gonna make it cute, no cap.


✨ NAME ✨

xstat_cm_test β€” Displays data collections from the Cache Manager


🌸 SYNOPSIS 🌸

xstat_cm_test [initcmd]
    -cmname <cache manager name(s) to monitor>+
    -collID <collection(s) to fetch>+ [-onceonly]
    [-frequency <poll frequency, in seconds>]
    [-period <data collection time, in minutes>] [-debug]
    [-version] [-help]

xstat_cm_test [i] -cm <cache manager name(s) to monitor>+
    -co <collection(s) to fetch>+ [-o]
    [-f <poll frequency, in seconds>]
    [-p <data collection time, in minutes>] [-d] [-version] [-h]

like, yes, there are two whole forms here β€” the long-form one and the short-flag one, and honestly the short one is giving speedrun energy πŸƒβ™€οΈπŸ’¨


πŸ¦‹ DESCRIPTION πŸ¦‹

so xstat_cm_test is the girl whose whole job is testing the routines in the libxstat_cm.a library πŸ’… and she displays the data collections that are associated with the Cache Manager. she runs in the foreground β€” no sneaky background behaviour, she's right there with you, main character energy.

heads up though: this command produces a large volume of output. like, a LOT. if you wanna save it for later analysis, direct it to a file. fr fr, do it, don't be the girl crying at her scrollback 🫢


πŸŽ€ OPTIONS πŸŽ€

  • initcmd β€” this one's just here to accommodate the command's use of the AFS command parser, and it's optional. the parser said "I need a spot" and we gave it one ✨
  • -cmname <cache manager name to monitor>+ β€” specifies the fully qualified hostname of each client machine whose Cache Manager you wanna monitor. you can pass more than one, hence the + πŸ‘‘
  • -collID <collection to fetch>+ β€” specifies each data collection to return, which is what defines the type and amount of data the command interpreter gathers about the Cache Manager. data comes back in a predefined data structure. you can ask for multiple collections. there are three acceptable values:
    • 0 β€” provides profiling information about the numbers of times different internal Cache Manager routines were called since the Cache Manager started.
    • 1 β€” reports various internal performance statistics related to the Cache Manager (for example, statistics about how effectively the cache is being used and the quantity of intracell and intercell data access).
    • 2 β€” reports all of the internal performance statistics that the 1 setting provides, plus some additional, detailed performance figures (for example, statistics about the number of RPCs sent by the Cache Manager and how long they take to complete, and statistics regarding authentication, access, and PAG information associated with data access). it's giving overachiever and we respect it πŸ’œ
  • -onceonly β€” gathers statistics just one time. omit this flag and the command will keep probing the Cache Manager for statistics at the frequency set by the -frequency argument β€” and in that case, press Ctrl+C to stop the probes. yes bestie, you have to stop it, she will not stop herself 😭
  • -frequency <poll frequency> β€” sets the frequency, in seconds, at which the program initiates probes to the Cache Manager. the default is 30 seconds. ⏰
  • -period <data collection time> β€” sets the number of minutes the program runs; at the end of this period of time, the program exits. the default is 10 minutes.
  • -debug β€” displays a trace on the standard output stream as the command runs. lil behind-the-scenes cam πŸŽ₯
  • -help β€” prints the online help for this command. all other valid options are ignored. (she's not multitasking, she's helping.)
  • -version β€” prints the program version and then exits. all other valid options are ignored. periodt. πŸ’…
also, if you peeped the second line of the synopsis, there are short-form flags living there: -cm, -co, -o, -f, -p, -d, and -h β€” that synopsis form is xstat_cm_test [i] -cm <cache manager name(s) to monitor>+ -co <collection(s) to fetch>+ [-o] [-f <poll frequency, in seconds>] [-p <data collection time, in minutes>] [-d] [-version] [-h]. so cute, so concise πŸŽ€

🌈 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.


okay that's the whole thing bestie, you ate it up πŸ’– this page is from OpenAFS, dated 2026-07-27, and it's hanging out in manual section 1 as XSTAT_CM_TEST(1). go forth and gather those data collections, no cap ✨🫢🌸

πŸ“¦ where this page comes from