On 5/31/17 3:27 PM, Cody P Schafer wrote:
>> RPC Ports are just the bindings into rpcbind. The tcp/udp ports are the
>> ones
>> that typically conflict and why this was all done to begin with.
>
> Ok, then it doesn't sound like that is a conflict or a "privileged
> ports" issue, and it is safe to drop the custom rpc program numbers
> ("RPC Ports") from `unfsd`s arguments & the kernel parameters.
>
> As I've noted, runqemu-export-rootfs does not register with rpcbind
> (we pass the `-p` flag to `unfsd`).
The rpcbind runs on a privileged port (usually). So either you have to 're-use'
the system wide on or run your own. On many environments, with a system wide
one, you will clash if someone else is offering the same services. So you are
forced to run your own and/or register then with a different set of port
numbers.
This is absolutely needed in a multi-user or 'locked system' configuration where
the user does not have permission to run these types of things.
--Mark
> Or is there something else system-wide which is keeping a list of rpc
> program numbers?
>
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
