On Thu, 25 Jan 2024 at 20:41, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > > The existing rpc.nfsd program was designed during a different time, when > we just didn't require that much control over how it behaved. It's > klunky to work with. > > In a response to Chuck's recent RFC patch to add knob to disable > READ_PLUS calls, I mentioned that it might be a good time to make a > clean break from the past and start a new program for controlling nfsd. > > Here's what I'm thinking: > > Let's build a swiss-army-knife kind of interface like git or virsh: > > # nfsdctl stats <--- fetch the new stats that got merged > # nfsdctl add_listener <--- add a new listen socket, by address or hostname Absolutely NOT "hostname". Please do not repeat the mistake AGAIN of separating "host name" and "TCP port", as they are both required to find the server. Every 10 or 15 years the same mistake is made by the next generation of software engineers. https://datatracker.ietf.org/doc/html/rfc1738 clearly defined "hostport", and that is what should be used here. Ced -- Cedric Blancher <cedric.blancher@xxxxxxxxx> [https://plus.google.com/u/0/+CedricBlancher/] Institute Pasteur
