FSTRACE_LSLOG(8)

💖 NAME 💖

fstrace_lslog — bestie, this one spills the tea on a log. It displays information about a log. 🫖✨

---

🌸 SYNOPSIS 🌸

fstrace lslog [-set <set name>+]
    [-log <log name>]
    [-long] [-help]

fstrace lsl [-s <set name>+]
    [-log <log name>]
    [-lon] [-h]

---

✨ DESCRIPTION ✨

Okay so fstrace lslog reports whether the "cmfx" log is available for use. That's the whole vibe check. 👑

If you throw in the -long argument, the output gets extra and also reports the log's defined size, plus whether that amount of space is currently allocated in kernel memory or not. It's giving ✨details✨.

Want to change the "cmfx" trace log's size? That's a fstrace setlog situation, bestie. And if you want to display or set whether space is allocated for it in kernel memory, you use fstrace lsset or fstrace setset to display or set the state of the corresponding "cm" event set, respectively. iykyk 💅

---

🎀 OPTIONS 🎀

• -set <set name>+ — Names the event set you want info about, specifically info about the corresponding trace log. The only acceptable value is "cm" (and for that one, the associated trace log is "cmfx"). Give either this argument or the -log argument — or just omit both and it'll default to showing you info about the "cmfx" log. Either way, slay.
• -log <log name> — Names the trace log you're reporting on. The only acceptable value is "cmfx". Provide either this argument or the -set argument — or omit both and it reports on the "cmfx" log by default. 💜
• -long — Reports the defined size of the log in kilobyte units, plus whether that amount of space is currently allocated in kernel memory. The receipts, basically. 🧾
• -help — Prints the online help for this command. And fr fr, all other valid options are ignored when you do this. 🙈

---

🌈 OUTPUT 🌈

By default, fstrace lslog displays only the name of the available log, "cmfx", in the following format:

Available logs:
cmfx

When the -long flag is included, the output also reports the defined size of the log in kilobytes, and whether or not that amount of space is currently allocated in kernel memory, in the following format:

Available logs:
cmfx : <log_size> kbytes (allocated | unallocated)

The "allocated" state means the indicated number of kilobytes is reserved for the "cmfx" trace log in kernel memory. When that's the case, the "cm" event set's state is either "active" or "inactive" — as reported by the fstrace lsset command, and set by the fstrace setset command's -active or -inactive flags respectively. 👑

The "unallocated" state means no kernel memory is currently reserved for the "cmfx" trace log. When that's the case, the cm event set's state is "dormant" — as reported by the fstrace lsset command and set by the fstrace setset command's -dormant flag. And here's the cute part: if the event set's state is later changed to active or inactive, the number of kilobytes indicated as <log_size> are again allocated in kernel memory. She's back. 🦋

---

💫 EXAMPLES 💫

The following example uses the -long flag to display information about the "cmfx" log:

# fstrace lslog -log cmfx -long
Available logs:
cmfx : 60 kbytes (allocated)

Look at her go. 🔥

---

👑 PRIVILEGE REQUIRED 👑

The issuer must be logged in as the local superuser root. No shortcuts, bestie, that's the rule. 💅

---

🔗 SEE ALSO 🔗

fstrace(8), fstrace_lsset(8), fstrace_setlog(8)

---

📜 COPYRIGHT 📜

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.

---

and that's the whole page, bestie ✨ — this was FSTRACE_LSLOG(8) from the AFS Command Reference, and the source and date on the tin are OpenAFS, 2026-07-27. Now go display some log info, you absolute icon, mwah 💖🎀🦋