This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| admin-nfs [2022/01/22 21:00] – clarity, grammar, formatting, add bullet options for Access hogwild | admin-nfs [2024/10/21 19:49] (current) – -Condense, formatting hogwild | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== NFS Server ===== | ===== NFS Server ===== | ||
| - | The built in NFS server | + | FreshTomato' |
| + | |||
| + | It's essentially the equivalent of Samba in a Linux environment. | ||
| + | |||
| + | \\ {{: | ||
| + | |||
| + | **Enable NFS Server:** sets the NFS server process to start at boot time. | ||
| \\ | \\ | ||
| + | |||
| + | **Enable legacy (NFS V2) support: **enables support for NFS version 2. | ||
| + | |||
| + | NFS currently has 3 versions - NFS 2/3/4. FreshTomato defaults to v3, but can also be set to " | ||
| \\ | \\ | ||
| - | {{: | + | **Exports**\\ |
| - | **Enable NFS Server** - Runs the NFS server process. | + | **Directory: |
| - | **Enable legacy (NFS V2) support** - NFS currenly has 3 version - NFS 2/3/4. FreshTomato defaults to v3, but with this option it can be enabled to " | + | \\ |
| - | **Exports**\\ {{: | + | **IP Address/ |
| - | **Directory** - This specifies the filesystem location to be shared. | + | \\ |
| - | **IP Address/ | + | **Access: |
| - | **Access** - Defines the share permissions (how the share can be accessed) | + | \\ |
| * Read-only | * Read-only | ||
| * Read/Write | * Read/Write | ||
| - | **Sync/ | + | \\ |
| + | |||
| + | **Sync/ | ||
| + | |||
| + | * Synchronous | ||
| + | |||
| + | * Async(hronous) - FreshTomato will acknowledge data before it's been written out. \\ The NFS server will acknowledge data before it's committed | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Subtree Check:** | ||
| + | |||
| + | * No * - subtree check will be disabled. | ||
| + | * Yes - enables subtree checking. | ||
| + | |||
| + | \\ | ||
| + | |||
| + | This has minor security implications, | ||
| + | |||
| + | In NFS, if a filesystem subdirectory is exported, but not the whole filesystem, then whenever a NFS request arrives, the server must check the accessed file is in the appropriate filesystem | ||
| + | |||
| + | To perform the check, the server must include details of the file location in the file handle given to the client. This can cause problems accessing files that are renamed while a client has them open. However, in many simple cases, it will still work. | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Other Options: | ||
| - | **Subtree_check** - Helps when one folder is exported but one or more of the subfolders is not. | + | Please refer to official NFS documentation for details. [[https:// |
| - | **Other_options** - Here you can specify advanced options. Please refer to the official NFS documentation for additional details.\\ | + | \\ \\ |