| Summary: | rpcbind: Could we replace portmap with rpcbind | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | LiRongQing <rongqing.li> |
| Component: | connectivity | Assignee: | Cristian Iorga <cristian.iorga> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | alexandru.c.georgescu, meta.mr.watcher, meta.watcher, rongqing.li, sgw |
| Version: | 1.3 | ||
| Target Milestone: | 1.4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | 9a1c99916bfc8b599e1fd567b0a61b979576b254 | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
LiRongQing
2012-07-22 02:11:08 UTC
What's the size difference in the binary? Can you summarize the feature differences, specifically are there any features that will be lost do to such a switch? Are there other conisderations? the size of rpcbind+rpcinfo is 240k the size of portmap+pmap_dump+pmap_set is 100k. I search on the network, only find that rpcbind has more feature than portmap, does not find that rpcbind lost feature than portmap Hello, Do you have any updates regarding rpcbind vs portmap? Thanks, Alex. NO Redhat, Fedora, debian, Ubuntu are using rpcbind by default, If do not using rpcbind, nfs can not work under ipv6 address, and nfs4 does not work. |