Is it just because the line in /etc/exports is crap, or I need some other configuration? or do I need the macOS Server app?įrom looking at it seems like it might not be anything I need the macOS Server app for?
Note: /path/to/my/shared/directory is obviously a just a placeholder filepath for this question, not my actual entry in /etc/exports 🤣 path/to/my/shared/directory 192.168.56.0/24(rw,fsid=root,all_squash,anonuid=1000,anongid=1000,no_subtree_check)Ĭalling nfsd checkexports returns the following: getaddrinfo() failed for 192.168.56.0/24(rw,fsid=root,all_squash,anonuid=1000,anongid=1000,no_subtree_check)Įxports:2: couldn't get address for host: 192.168.56.0/24(rw,fsid=root,all_squash,anonuid=1000,anongid=1000,no_subtree_check)Įxports:2: no valid hosts found for exportĪnd if I simplify and change the etc/exports entry to /path/to/my/shared/directory -network 192.168.56.0 -mask 255.255.255.0 I get the following output from nfsd checkexports: exports:2: path contains non-directory or non-existent components: /path/to/my/shared/directoryĮxports:2: no usable directories in export entry and no fallback My regular line in /etc/exports on Linux: # NFS Share to Virtualbox guests: This is something I am used to doing in Linux without any difficulty, but the syntax for /etc/exports doesn't seem to be the same? In the man page for exports on macOS it uses explicit flags?
First of all, I'm happy to pay the $19.99 for the Mac OS Server app from the app store, so that's no problem, it's just that at the moment I only have one specific need - NFS sharing between my macOS sierra host and a virtualbox VM guest running Debian Sarge (don't ask).
0 kommentar(er)
