{
    "mode": "man",
    "parameter": "RPC_XDR",
    "section": "3",
    "url": "https://www.chedong.com/phpMan.php/man/RPC_XDR/3/json",
    "generated": "2026-05-30T11:54:35Z",
    "synopsis": "",
    "sections": {
        "NAME": {
            "content": "xdracceptedreply, xdrauthsysparms, xdrcallhdr, xdrcallmsg, xdropaqueauth,\nxdrrejectedreply, xdrreplymsg — XDR library routines for remote procedure calls\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "",
            "subsections": [
                {
                    "name": "#include <rpc/rpc.h>",
                    "content": "boolt\nxdracceptedreply(XDR *xdrs, struct acceptedreply *ar);\n\nboolt\nxdrauthsysparms(XDR *xdrs, struct authsysparms *aupp);\n\nboolt\nxdrcallhdr(XDR *xdrs, struct rpcmsg *chdr);\n\nboolt\nxdrcallmsg(XDR *xdrs, struct rpcmsg *cmsg);\n\nboolt\nxdropaqueauth(XDR *xdrs, struct opaqueauth *ap);\n\nboolt\nxdrrejectedreply(XDR *xdrs, struct rejectedreply *rr);\n\nboolt\nxdrreplymsg(XDR *xdrs, struct rpcmsg *rmsg);\n"
                }
            ]
        },
        "DESCRIPTION": {
            "content": "These routines are used for describing the RPC messages in XDR language.  They should normally\nbe used by those who do not want to use the RPC package directly.  These routines return TRUE\nif they succeed, FALSE otherwise.\n",
            "subsections": []
        },
        "Routines": {
            "content": "See rpc(3) for the definition of the XDR data structure.\n\nxdracceptedreply()\nUsed to translate between RPC reply messages and their external representation.  It in‐\ncludes the status of the RPC call in the XDR language format.  In the case of success,\nit also includes the call results.\n\nxdrauthsysparms()\nUsed for describing UNIX operating system credentials.  It includes machine-name, uid,\ngid list, etc.\n\nxdrcallhdr()\nUsed for describing RPC call header messages.  It encodes the static part of the call\nmessage header in the XDR language format.  It includes information such as transaction\nID, RPC version number, program and version number.\n\nxdrcallmsg()\nUsed for describing RPC call messages.  This includes all the RPC call information such\nas transaction ID, RPC version number, program number, version number, authentication\ninformation, etc.  This is normally used by servers to determine information about the\nclient RPC call.\n\nxdropaqueauth()\nUsed for describing RPC opaque authentication information messages.\n\nxdrrejectedreply()\nUsed for describing RPC reply messages.  It encodes the rejected RPC message in the XDR\nlanguage format.  The message could be rejected either because of version number mis-\nmatch or because of authentication errors.\n\nxdrreplymsg()\nUsed for describing RPC reply messages.  It translates between the RPC reply message and\nits external representation.  This reply could be either an acceptance, rejection or\nNULL.\n",
            "subsections": []
        },
        "AVAILABILITY": {
            "content": "These functions are part of libtirpc.\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "rpc(3), xdr(3)\n\nBSD                               May 3, 1993                              BSD",
            "subsections": []
        }
    },
    "summary": "xdracceptedreply, xdrauthsysparms, xdrcallhdr, xdrcallmsg, xdropaqueauth, xdrrejectedreply, xdrreplymsg — XDR library routines for remote procedure calls",
    "flags": [],
    "examples": [],
    "see_also": [
        {
            "name": "rpc",
            "section": "3",
            "url": "https://www.chedong.com/phpMan.php/man/rpc/3/json"
        },
        {
            "name": "xdr",
            "section": "3",
            "url": "https://www.chedong.com/phpMan.php/man/xdr/3/json"
        }
    ]
}