Fix docs regarding "noforget"

mkdocs/docs/config/deprecated_options.md

@@ -7,14 +7,15 @@ function or have been replaced. **They should not be used.**
   automatically if running as root.
 * **async_read**: Use `async-read=true`.
 * **atomic_o_trunc**: Does nothing.
-* **big_writes**: Does nothing.
 * **attr_timeout**: Use [cache.attr](cache.md).
 * **auto_cache**: Use [cache.files=auto-full](cache.md).
+* **big_writes**: Does nothing.
 * **direct_io**: Use [cache.files=off](cache.md).
 * **entry_timeout**: Use [cache.entry](cache.md).
 * **hard_remove**: Does nothing.
 * **kernel_cache**: Use [cache.files=full](cache.md).
 * **negative_entry**: Use [cache.negative-entry](cache.md).
+* **noforget**: Use `never-forget-nodes`.
 * **nonempty**: Does nothing.
 * **splice_move**: Does nothing.
 * **splice_read**: Does nothing.

mkdocs/docs/config/options.md

@@ -217,7 +217,8 @@ config file.
   representation of a file once the OS tells mergerfs it is no longer
   needed. Really only needed for [exporting mergerfs via
   NFS](../remote_filesystems.md) (default: 0)
-* **noforget**: Effectively sets `remember-nodes` to infinity.
+* **never-forget-nodes=BOOL**: Sets `remember-nodes` to
+  infinity. Formerly `noforget`. (default: false)
 * **allow-idmap=BOOL**: Enables idmap (identity mapping). (default:
   true)
 * **debug**: Enable debugging information. At the moment limited to a

mkdocs/docs/remote_filesystems.md

@@ -80,17 +80,17 @@ but if you run into problems it may be worth trying Samba/SMB.
 * `inodecalc=path-hash`
 * `lazy-umount-mountpoint=false`
 
-`noforget` (or `remember-nodes` with a large value such as `86400` for
-a full day) is needed because NFS uses the `name_to_handle_at` and
-`open_by_handle_at` functions which allow a program to keep a
-reference to a file without technically having it open in the typical
-sense. The problem is that FUSE has no way to know that NFS has a
-handle that it will later use to open the file again. As a result, it
-is possible for the kernel to tell mergerfs to forget about the file
-node and should NFS ever ask for that node's details in the future it
-would have nothing to respond with. Keeping nodes around forever (or
-however long is set with `remember-nodes`) is not ideal but at the
-moment the only way to manage the situation.
+`never-forget-nodes=true` (or `remember-nodes` with a large value such
+as `86400` for a full day) is needed because NFS uses the
+`name_to_handle_at` and `open_by_handle_at` functions which allow a
+program to keep a reference to a file without technically having it
+open in the typical sense. The problem is that FUSE has no way to know
+that NFS has a handle that it will later use to open the file
+again. As a result, it is possible for the kernel to tell mergerfs to
+forget about the file node and should NFS ever ask for that node's
+details in the future it would have nothing to respond with. Keeping
+nodes around forever (or however long is set with `remember-nodes`) is
+not ideal but at the moment the only way to manage the situation.
 
 `inodecalc=path-hash` is needed because NFS is sensitive to
 out-of-band changes. FUSE doesn't care if a file's inode value changes

mkdocs/docs/resource_usage.md

@@ -12,7 +12,7 @@
       depending on [fuse-msg-size](config/fuse-msg-size.md)
     * buffers allocated temporarily for reading directories
     * FUSE nodes
-    * noforget forgotten nodes
+    * never-forget-nodes=true nodes
 
 
 ## Management