RPC_SVC_ERR(3)

✨ RPC_SVC_ERR(3) — server-side RPC error routines, bestie edition ✨

okay so this is a page from the Library Functions Manual (section 3, the C library girlies 💅), and it's all about the little error-reporting glow-ups your RPC server can use. no cap, if you're writing a server that talks to other machines over the network, this is your moment. 🫶

---

🌸 NAME 🌸

rpc_svc_err, svcerr_auth, svcerr_decode, svcerr_noproc, svcerr_noprog, svcerr_progvers, svcerr_systemerr, svcerr_weakauth — literally a whole friend group of library routines for server side remote procedure call errors. they handle the awkward moments so your dispatch function doesn't have to. 💖

🎀 LIBRARY 🎀

Standard C Library (libc, -lc) — she's iconic, she's everywhere.

✨ SYNOPSIS ✨

#include <rpc/rpc.h>

void
svcerr_auth(SVCXPRT *xprt, enum auth_stat why);

void
svcerr_decode(SVCXPRT *xprt);

void
svcerr_noproc(SVCXPRT *xprt);

void
svcerr_noprog(SVCXPRT *xprt);

void
svcerr_progvers(SVCXPRT *xprt, rpcvers_t low_vers, rpcvers_t high_vers);

void
svcerr_systemerr(SVCXPRT *xprt);

void
svcerr_weakauth(SVCXPRT *xprt);

🦋 DESCRIPTION 🦋

these routines are part of the RPC library, which is the whole vibe that lets C language programs make procedure calls on other machines across the network. like, your code reaching out and touching someone else's code. on a different computer. ✨

so the tea is: these routines can be called by the server side dispatch function if there's any error in the transaction with the client. think of it as the server going "bestie, something went wrong, and here's exactly which something." 😭

🌈 Routines 🌈

see rpc(3) for the definition of the SVCXPRT data structure. yes, you need it. go look. 👀

• svcerr_auth() — called by a service dispatch routine that refuses to perform a remote procedure call because of an authentication error. like, sorry babe, you're not on the list. 🙈
• svcerr_decode() — called by a service dispatch routine that can't successfully decode the remote arguments (see svc_getargs() in rpc_svc_reg(3)). the args arrived and they're giving corrupted file energy. 💀
• svcerr_noproc() — called by a service dispatch routine that does not implement the procedure number that the caller requests. wrong procedure, bestie, we don't do that one here.
• svcerr_noprog() — called when the desired program is not registered with the RPC package. service implementors usually do not need this routine. (not you, bestie, you probably don't need it 💅)
• svcerr_progvers() — called when the desired version of a program is not registered with the RPC package. the low_vers argument is the lowest version number, and high_vers is the highest version number. service implementors usually do not need this routine either — it's giving "handled for you, don't worry about it." ✨
• svcerr_systemerr() — called by a service dispatch routine when it detects a system error not covered by any particular protocol. for example, if a service can no longer allocate storage, it may call this routine. out of memory? she's calling this. the catch-all of catch-alls. 🔥
• svcerr_weakauth() — called by a service dispatch routine that refuses to perform a remote procedure call due to insufficient (but correct) authentication arguments. so the creds are real, they're just not enough — the routine calls svcerr_auth(xprt, AUTH_TOOWEAK). it's giving "you're valid but you're not that valid." 💅

ngl, these all take an SVCXPRT *xprt — that's your transport handle, your connection to the client. keep her close. 🫶

👑 SEE ALSO 👑

rpc(3), rpc_svc_calls(3), rpc_svc_create(3), rpc_svc_reg(3)

---

and that's the whole page, bestie!! this one's from the Debian flavor of the manual, dated May 3, 1993 — yes, she's a vintage icon and she ATE. periodt. 💖✨🎀