PLOCKSTAT(1)

πŸ“¦ version 15.1, in freebsd 14.5, freebsd 15.1

πŸ’– NAME πŸ’–

okay so this is plockstat(1), and yes bestie, it's lowkey from the General Commands Manual β€” we're tracing pthread locks today and it's giving main character energy πŸ’…

plockstat β€” Trace pthread lock statistics using DTrace ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

plockstat [-vACHV] [-n count] [-s depth] [-e secs] [-x opt=val] command
          [arg...]
plockstat [-vACHV] [-n count] [-s depth] [-e secs] [-x opt=val] -p pid

🌸 DESCRIPTION 🌸

The plockstat utility traces pthread locks β€” that's mutexes and rwlocks, bestie β€” and prints statistics about them. You can use plockstat to investigate bottlenecks in your software. Literally so useful for finding out where your code is being slow and dramatic 😭

The following options are available:

  • -v β€” Be verbose. Spill the tea, queen πŸ’¬
  • -A β€” Print all statistics. All of them. No crumbs πŸ™ˆ
  • -C β€” Print commulative statistics (the default). Yes, that's the spelling in the original β€” we keep it, periodt πŸ’…
  • -H β€” Print a histogram. It's giving data visualization slay πŸ“Š
  • -V β€” Print the DTrace script about to be used to stderr. Peek behind the curtain, iykyk πŸŽ€
  • -n count β€” Set the aggregation count for the data set. Numbers, but make it cute πŸ”’
  • -s depth β€” Set the ustack (userland stack) caller depth. Get that stack depth, bestie 🧚
  • -e secs β€” Does nothing at the moment. She's just vibing 😭
  • -x opt=val β€” Specify DTrace options. See the dtrace(1) man page for more details πŸ‘‘

⭐ EXIT STATUS ⭐

The plockstat utility exits 0 on success, and >0 if an error occurs. So 0 is the slay outcome, and anything above is the "not me, not today" outcome πŸ’€


🌈 SEE ALSO 🌈


πŸ‘‘ HISTORY πŸ‘‘

The plockstat utility comes from OpenSolaris and was first imported into FreeBSD 9.0 β€” a whole origin story, honestly 🫢


This page is from Debian, dated September 13, 2010 β€” mwah, periodt πŸ’‹πŸ’–

πŸ“¦ where this page comes from