PROBE::SUNRPC.SVC.SEND(3stap)

💖 probe::sunrpc.svc.send — the 3stap page, bestie edition 💖

okay so you opened PROBE::SUNRPC.SVC() in the 3stap manual and honestly? iconic of you. this is the probe that fires when the RPC server is sending the reply back to the client. it's giving "here's your answer, bye" energy 🫶

---

✨ NAME ✨

probe::sunrpc.svc.send — Return reply to RPC client

like literally. the reply goes back to the RPC client. that's the whole vibe. 📬

---

🌸 SYNOPSIS 🌸

probe sunrpc.svc.send {}

no arguments, no drama, no parameters to pass in. she just shows up when she's needed 💅

---

🎀 VALUES 🎀

every one of these is a local variable you can peek at while the probe is running. read them, love them, print them in your printf ✨

• peer_ip — the peer address where the request is from. so like, who is asking 🫵
• rq_xid — the transmission id in the request. her little serial number so everybody can keep the requests straight 👑
• rq_prog — the program number in the request. which RPC program we're talking to, fr fr 🌈
• rq_proc — the procedure number in the request. the specific procedure inside that program, iykyk 🧚
• rq_prot — the IP protocol of the request. yes bestie, this is the protocol — the manpage says "reqeust" but we all know what she meant 😭💀
• rq_vers — the program version in the request. because programs have eras and eras have numbers 💜
• sv_name — the service name. the name of the service, babes, it's right there in the label 🌸

ngl every single one of these is worth grabbing in your probe body — they're the whole reason this probe is main character energy.

---

👑 SEE ALSO 👑

• tapset::rpc(3stap) — go read the rpc tapset page too, it's the bestie to this one 💖

---

okay that's the whole page, no cap. this was the PROBE::SUNRPC.SVC() page from the 3stap manual — go slay some RPC tracing, and remember: reply sent, vibe secured. 💅✨🦋