rpc(3nsl): svc_sendreply is in rpc_svc_calls(3nsl)
The rpc(3nsl) man page says:
Index to Routines The following table lists RPC routines and the manual reference pages on which they are described: RPC Routine Manual Reference Page ... svc_sendreply rpc_svc_reg(3NSL)
That's not true. The svc_sendreply is actually documented in rpc_svc_calls(3nsl). The whole list in rpc(3nsl) should be checked too to be sure there are no other similar issues there.
Updated by Marcel Telka about 6 years ago
Similar issue is in rpc_svc_err(3nsl) man page, where it is stated this:
void svcerr_decode(const SVCXPRT *xprt); Called by a service dispatch routine that cannot suc- cessfully decode the remote parameters (see svc_getargs() in rpc_svc_reg(3NSL)).
But the svc_getargs() is documented in rpc_svc_calls(3nsl).
Updated by Marcel Telka almost 6 years ago
Minor typo in rpc(3nsl):
Nettyp Some of the high-level RPC interface routines take a nettype string as one of the parameters (for example, clnt_create(), svc_create(), rpc_reg(), rpc_call()). This string defines a class of transports which can be used for a particular
Nettyp should be changed to Nettype.
Updated by Electric Monk about 5 years ago
- Status changed from Pending RTI to Closed
- % Done changed from 0 to 100
commit 22fec8cf7c90530cbbeb80ea11190db467cb2e21 Author: Marcel Telka <email@example.com> Date: 2014-11-24T21:42:20.000Z 4305 rpc(3nsl): svc_sendreply is in rpc_svc_calls(3nsl) Reviewed by: Richard Lowe <firstname.lastname@example.org> Reviewed by: Gordon Ross <email@example.com> Reviewed by: Yuri Pankov <firstname.lastname@example.org> Approved by: Dan McDonald <email@example.com>