🚀 go-pugleaf

>registerrpc will register a prog#/ver# with portmapper. Portmapper assigns the
>port #.

No, it doesn't.  The portmapper doesn't assign port numbers (take a look
at RFC 1057, which describes the portmapper's RPC protocol; there ain't
no call in there that *chooses* a port number and *assigns* it to a
server - there's just a PMAPPROC_SET call to bind an *already-allocated*
port number to a particular program and version number and Internet
protocol number); other code does (for example, the UDP or TCP
implementation, at least in UNIX systems).

If all you want to do is just register a port number with the portmapper
as being bound to some particular program and version number for some
particular protocol, you can do so with "pmap_set()".

The advantage of using "pmap_set()" rather than "registerrpc()" is that
you don't set up all the rest of the RPC mechanism; given that the
original poster didn't *want* to drag in the rest of the RPC mechanism,
that's probably what they want.

>svc_unregister() removes the entry.

So does "pmap_unset()", and it also doesn't pester the rest of the RPC
mechanism.