On Fri, Jun 30, 2017 at 11:25:31AM -0400, Steve Dickson wrote: > On 06/30/2017 09:21 AM, Stefan Hajnoczi wrote: > > The following command-line serves NFSv4.1 over AF_VSOCK: > > > > nfsd -TU -N3 -V4.1 -v 2049 > So this specifying no-tcp, no-udp (which is no longer needed since > udp is off by default), no-v3, only-v4.1, vsock listiner, > and you are missing a -p because I don't think you want to > start up 2049 process. -v takes an argument (the AF_VSOCK port number to listen on), so the 2049 is consumed and not interpreted as the number of processes. > How does this work with the standard NFS server? Are the > co-compatible? I'll test tcp + vsock in a single nfsd and make sure it works for the next revision of this patch series. Nothing in the kernel or nfs-utils code intentionally prevents them from being used at the same time. My intention is that /etc/exports dictates which exports are visible over TCP, vsock, or both. > Also the --vsock needs to be documented. Also can the > --vsock flag just mean all of these specifics... Meaning > so they don't have to be specified on the command line? Thanks, will document the --vsock <port> option.
Attachment:
signature.asc
Description: PGP signature
