PROBE::SUNRPC.CLNT(3stap)

💫 PROBE::SUNRPC.CLNT — the sunrpc.clnt tapset (section 3stap, Networking Tapset, bestie) 💫

okay so real talk: this page is probe::sunrpc.clnt.call_async from the SystemTap tapset fam, and it lives in the Networking Tapset. if you're poking at RPC calls in the kernel and you want to catch them while they fly, this is your girl. periodt.

---

✨ NAME ✨

probe::sunrpc.clnt.call_async — Make an asynchronous RPC call

like, you're not waiting around for the answer. you fire it off and keep it moving. main character energy fr fr. 🔥

---

🦋 SYNOPSIS 🦋

probe sunrpc.clnt.call_async {}

that's it. no args, no params, no nothing. she's a probe, she doesn't need your input. 💅

---

🎀 VALUES 🎀

these are the local variables you get to peek at inside the probe handler. every single one, no skips, no cap:

• prog — the RPC program number 👑
• vers — the RPC program version number
• procname — the procedure name in this RPC call 🌸
• flags — flags. that's the whole vibe. flags.
• xid — current transmission id (this is the lil tracking number for the call, iykyk)
• servername — the server machine name 🫶
• prot — the IP protocol number
• port — the port number
• progname — the RPC program name ✨
• proc — the procedure number in this RPC call
• dead — whether this client is abandoned 💀 (yes literally, dead is the name, not me being dramatic for once)

ngl the difference between procname and proc trips people up: one's the name (string), one's the number. and prog vs progname is the exact same situation. iconic duo behaviour. 🙈

---

🌈 SEE ALSO 🌈

• tapset::rpc(3stap) — go read this one next, bestie, it's the whole rpc tapset 🧚

---

that's the whole page!! nothing else hiding in there, I checked twice. go forth and trace some async RPC calls, you absolute legend. 🍓

SystemTap Tapset Reference, Version (the version string got cut off in the header, so just know it's the SystemTap Tapset Reference), dated September 2026 — manual page PROBE::SUNRPC.CLNT(3stap). mwah, bye!! 💖