RPC_GSS_SVC_MAX_DATA_LENGTH(3)

📦 version 15.1, in freebsd 14.5, freebsd 15.1

okay bestie, this is the RPC_GSS_SVC_MAX_DATA_LEN(3) page from the Library Functions Manual — and yes, the header really does repeat RPC_GSS_SVC_MAX_DATA_LEN(3) twice, because two-column headers are extra like that 💅. The actual function we're hyping is rpc_gss_svc_max_data_length (the footer later says RPC_GSS_SVC_MAX_DATA_LENGTH(3), so keep that plot twist in mind 👀).

🌸 NAME 🌸

rpc_gss_svc_max_data_length — calculate maximum data size

🫶 LIBRARY 🫶

It lives in the RPC GSS-API Authentication Library (librpcsec_gss, -lrpcsec_gss). iconic.

✨ SYNOPSIS ✨

#include <rpc/rpcsec_gss.h>

int
rpc_gss_svc_max_data_length(struct svc_req *req, int max_tp_unit_len);

💖 DESCRIPTION 💖

Calculate the maximum message size that will fit into a packet of size max_tp_unit_len, given the current service and QoP setting. no cap, that's the whole assignment 🎀.

🦋 PARAMETERS 🦋

  • req — an RPC request 👑
  • max_tp_unit_len — maximum packet size of the underlying transport protocol 📦

⭐ RETURN VALUES ⭐

The maximum message size that can be encoded. that's it, that's the return ✨.

🌈 SEE ALSO 🌈

iykyk, go read the friends 💜.

🧚 HISTORY 🧚

The rpc_gss_svc_max_data_length function first appeared in FreeBSD 8.0. periodt 🫶.

🎀 AUTHORS 🎀

This manual page was written by Doug Rabson <dfr@FreeBSD.org>.

mwah 💋 — brought to you by Debian, dated January 26, 2010, with footer energy reading RPC_GSS_SVC_MAX_DATA_LENGTH(3). bye bestie! 🫶

📦 where this page comes from