{
    "content": [
        {
            "type": "text",
            "text": "# rpcinfo (info)\n\n## NAME\n\nrpcinfo -- report RPC information\n\n## SYNOPSIS\n\nrpcinfo [-m | -s] [host]\nrpcinfo -p [host]\nrpcinfo -T transport host prognum [versnum]\nrpcinfo -l [-T transport] host prognum versnum\nrpcinfo [-n portnum] -u host prognum [versnum]\nrpcinfo [-n portnum] [-t] host prognum [versnum]\nrpcinfo -a servaddress -T transport prognum [versnum]\nrpcinfo -b [-T transport] prognum versnum\nrpcinfo -d [-T transport] prognum versnum\n\n## DESCRIPTION\n\nrpcinfo makes an RPC call to an RPC server and reports what it finds.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS**\n- **EXAMPLES**\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "rpcinfo",
        "section": "",
        "mode": "info",
        "summary": "rpcinfo -- report RPC information",
        "synopsis": "rpcinfo [-m | -s] [host]\nrpcinfo -p [host]\nrpcinfo -T transport host prognum [versnum]\nrpcinfo -l [-T transport] host prognum versnum\nrpcinfo [-n portnum] -u host prognum [versnum]\nrpcinfo [-n portnum] [-t] host prognum [versnum]\nrpcinfo -a servaddress -T transport prognum [versnum]\nrpcinfo -b [-T transport] prognum versnum\nrpcinfo -d [-T transport] prognum versnum",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [
            "To show all of the RPC services registered on the local machine use:",
            "example% rpcinfo",
            "To show all of the RPC services registered with rpcbind on the machine",
            "named klaxon use:",
            "example% rpcinfo klaxon",
            "The information displayed by the above commands can be quite lengthy.",
            "Use the -s option to display a more concise list:",
            "example$ rpcinfo -s klaxon",
            "program   version   netid                     service    owner",
            "100000    2,3,4     local,tcp,udp,tcp6,udp6   rpcbind    super-user",
            "100008    1         udp,tcp,udp6,tcp6         walld      super-user",
            "100002    2,1       udp,udp6                  rusersd    super-user",
            "100001    2,3,4     udp,udp6                  rstatd     super-user",
            "100012    1         udp,tcp                   sprayd     super-user",
            "100007    3         udp,tcp                   ypbind     super-user",
            "To show whether the RPC service with program number prognum and version",
            "versnum is registered on the machine named klaxon for the transport TCP",
            "use:",
            "example% rpcinfo -T tcp klaxon prognum versnum",
            "To show all RPC services registered with version 2 of the rpcbind proto-",
            "col on the local machine use:",
            "example% rpcinfo -p",
            "To delete the registration for version 1 of the walld (program number",
            "100008 ) service for all transports use:",
            "example# rpcinfo -d 100008 1",
            "or",
            "example# rpcinfo -d walld 1"
        ],
        "see_also": [
            {
                "name": "rpc",
                "section": "3",
                "url": "https://www.chedong.com/phpMan.php/man/rpc/3/json"
            },
            {
                "name": "netconfig",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/netconfig/5/json"
            },
            {
                "name": "rpc",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/rpc/5/json"
            },
            {
                "name": "rpcbind",
                "section": "8",
                "url": "https://www.chedong.com/phpMan.php/man/rpcbind/8/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 10,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 27,
                "subsections": []
            },
            {
                "name": "OPTIONS",
                "lines": 71,
                "subsections": []
            },
            {
                "name": "EXAMPLES",
                "lines": 42,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 3,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "rpcinfo -- report RPC information\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "rpcinfo [-m | -s] [host]\nrpcinfo -p [host]\nrpcinfo -T transport host prognum [versnum]\nrpcinfo -l [-T transport] host prognum versnum\nrpcinfo [-n portnum] -u host prognum [versnum]\nrpcinfo [-n portnum] [-t] host prognum [versnum]\nrpcinfo -a servaddress -T transport prognum [versnum]\nrpcinfo -b [-T transport] prognum versnum\nrpcinfo -d [-T transport] prognum versnum\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "rpcinfo makes an RPC call to an RPC server and reports what it finds.\n\nIn the first synopsis, rpcinfo lists all the registered RPC services with\nrpcbind on host.  If host is not specified, the local host is the de-\nfault.  If -s is used, the information is displayed in a concise format.\n\nIn the second synopsis, rpcinfo lists all the RPC services registered\nwith rpcbind, version 2.  Also note that the format of the information is\ndifferent in the first and the second synopsis.  This is because the sec-\nond synopsis is an older protocol used to collect the information dis-\nplayed (version 2 of the rpcbind protocol).\n\nThe third synopsis makes an RPC call to procedure 0 of prognum and\nversnum on the specified host and reports whether a response was re-\nceived.  transport is the transport which has to be used for contacting\nthe given service.  The remote address of the service is obtained by mak-\ning a call to the remote rpcbind.\n\nThe prognum argument is a number that represents an RPC program number.\nIf a versnum is specified, rpcinfo attempts to call that version of the\nspecified prognum.  Otherwise, rpcinfo attempts to find all the regis-\ntered version numbers for the specified prognum by calling version 0,\nwhich is presumed not to exist; if it does exist, rpcinfo attempts to ob-\ntain this information by calling an extremely high version number in-\nstead, and attempts to call each registered version.  Note: the version\nnumber is required for -b and -d options.\n",
                "subsections": []
            },
            "OPTIONS": {
                "content": "-T transport\nSpecify the transport on which the service is required.  If this\noption is not specified, rpcinfo uses the transport specified in\nthe NETPATH environment variable, or if that is unset or null,\nthe transport in the netconfig(5) database is used.  This is a\ngeneric option, and can be used in conjunction with other options\nas shown in the SYNOPSIS.\n\n-a servaddress\nUse servaddress as the (universal) address for the service on\ntransport to ping procedure 0 of the specified prognum and report\nwhether a response was received.  The -T option is required with\nthe -a option.\n\nIf versnum is not specified, rpcinfo tries to ping all available\nversion numbers for that program number.  This option avoids\ncalls to remote rpcbind to find the address of the service.  The\nservaddress is specified in universal address format of the\ngiven transport.\n\n-b      Make an RPC broadcast to procedure 0 of the specified prognum and\nversnum and report all hosts that respond.  If transport is spec-\nified, it broadcasts its request only on the specified transport.\nIf broadcasting is not supported by any transport, an error mes-\nsage is printed.  Use of broadcasting should be limited because\nof the potential for adverse effect on other systems.\n\n-d      Delete registration for the RPC service of the specified prognum\nand versnum.  If transport is specified, unregister the service\non only that transport, otherwise unregister the service on all\nthe transports on which it was registered.  Only the owner of a\nservice can delete a registration, except the super-user who can\ndelete any service.\n\n-l      Display a list of entries with a given prognum and versnum on the\nspecified host.  Entries are returned for all transports in the\nsame protocol family as that used to contact the remote rpcbind.\n\n-m      Display a table of statistics of rpcbind operations on the given\nhost.  The table shows statistics for each version of rpcbind\n(versions 2, 3 and 4), giving the number of times each procedure\nwas requested and successfully serviced, the number and type of\nremote call requests that were made, and information about RPC\naddress lookups that were handled. This is useful for monitoring\nRPC activities on host.\n\n-n portnum\nUse portnum as the port number for the -t and -u options instead\nof the port number given by rpcbind.  Use of this option avoids a\ncall to the remote rpcbind to find out the address of the ser-\nvice. This option is made obsolete by the -a option.\n\n-p      Probe rpcbind on host using version 2 of the rpcbind protocol,\nand display a list of all registered RPC programs.  If host is\nnot specified, it defaults to the local host.  Note: Version 2 of\nthe rpcbind protocol was previously known as the portmapper pro-\ntocol.\n\n-s      Display a concise list of all registered RPC programs on host.\nIf host is not specified, it defaults to the local host.\n\n-t      Make an RPC call to procedure 0 of prognum on the specified host\nusing TCP, and report whether a response was received. This op-\ntion is made obsolete by the -T option as shown in the third syn-\nopsis.\n\n-u      Make an RPC call to procedure 0 of prognum on the specified host\nusing UDP, and report whether a response was received. This op-\ntion is made obsolete by the -T option as shown in the third syn-\nopsis.\n",
                "subsections": []
            },
            "EXAMPLES": {
                "content": "To show all of the RPC services registered on the local machine use:\n\nexample% rpcinfo\n\nTo show all of the RPC services registered with rpcbind on the machine\nnamed klaxon use:\n\nexample% rpcinfo klaxon\n\nThe information displayed by the above commands can be quite lengthy.\nUse the -s option to display a more concise list:\n\nexample$ rpcinfo -s klaxon\n\nprogram   version   netid                     service    owner\n100000    2,3,4     local,tcp,udp,tcp6,udp6   rpcbind    super-user\n100008    1         udp,tcp,udp6,tcp6         walld      super-user\n100002    2,1       udp,udp6                  rusersd    super-user\n100001    2,3,4     udp,udp6                  rstatd     super-user\n100012    1         udp,tcp                   sprayd     super-user\n100007    3         udp,tcp                   ypbind     super-user\n\nTo show whether the RPC service with program number prognum and version\nversnum is registered on the machine named klaxon for the transport TCP\nuse:\n\nexample% rpcinfo -T tcp klaxon prognum versnum\n\nTo show all RPC services registered with version 2 of the rpcbind proto-\ncol on the local machine use:\n\nexample% rpcinfo -p\n\nTo delete the registration for version 1 of the walld (program number\n100008 ) service for all transports use:\n\nexample# rpcinfo -d 100008 1\n\nor\n\nexample# rpcinfo -d walld 1\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "rpc(3), netconfig(5), rpc(5), rpcbind(8)\n\nAugust 18, 1992",
                "subsections": []
            }
        }
    }
}