docs: restore lost VFS poll interval docs

These came from 3d475dc0ee which unfortunately got added the
docs to the auto generated files.

docs/content/commands/rclone_mount.md

@@ -1,5 +1,5 @@
 ---
-date: 2020-02-10T14:50:44Z
+date: 2020-02-10T14:59:49Z
 title: "rclone mount"
 slug: rclone_mount
 url: /commands/rclone_mount/
@@ -188,7 +188,9 @@ Using the `--dir-cache-time` flag, you can set how long a
 directory should be considered up to date and not refreshed from the
 backend. Changes made locally in the mount may appear immediately or
 invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires.
+be picked up once the cache expires if the backend configured does not
+support polling for changes. If the backend supports polling, changes
+will be picked up on within the polling interval.
 
 Alternatively, you can send a `SIGHUP` signal to rclone for
 it to flush all directory caches, regardless of how old they are.

docs/content/commands/rclone_serve_dlna.md

@@ -1,5 +1,5 @@
 ---
-date: 2020-02-10T14:50:44Z
+date: 2020-02-10T14:59:49Z
 title: "rclone serve dlna"
 slug: rclone_serve_dlna
 url: /commands/rclone_serve_dlna/
@@ -39,7 +39,9 @@ Using the `--dir-cache-time` flag, you can set how long a
 directory should be considered up to date and not refreshed from the
 backend. Changes made locally in the mount may appear immediately or
 invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires.
+be picked up once the cache expires if the backend configured does not
+support polling for changes. If the backend supports polling, changes
+will be picked up on within the polling interval.
 
 Alternatively, you can send a `SIGHUP` signal to rclone for
 it to flush all directory caches, regardless of how old they are.

docs/content/commands/rclone_serve_ftp.md

@@ -1,5 +1,5 @@
 ---
-date: 2020-02-10T14:50:44Z
+date: 2020-02-10T14:59:49Z
 title: "rclone serve ftp"
 slug: rclone_serve_ftp
 url: /commands/rclone_serve_ftp/
@@ -38,7 +38,9 @@ Using the `--dir-cache-time` flag, you can set how long a
 directory should be considered up to date and not refreshed from the
 backend. Changes made locally in the mount may appear immediately or
 invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires.
+be picked up once the cache expires if the backend configured does not
+support polling for changes. If the backend supports polling, changes
+will be picked up on within the polling interval.
 
 Alternatively, you can send a `SIGHUP` signal to rclone for
 it to flush all directory caches, regardless of how old they are.

docs/content/commands/rclone_serve_http.md

@@ -1,5 +1,5 @@
 ---
-date: 2020-02-10T14:50:44Z
+date: 2020-02-10T14:59:49Z
 title: "rclone serve http"
 slug: rclone_serve_http
 url: /commands/rclone_serve_http/
@@ -87,7 +87,9 @@ Using the `--dir-cache-time` flag, you can set how long a
 directory should be considered up to date and not refreshed from the
 backend. Changes made locally in the mount may appear immediately or
 invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires.
+be picked up once the cache expires if the backend configured does not
+support polling for changes. If the backend supports polling, changes
+will be picked up on within the polling interval.
 
 Alternatively, you can send a `SIGHUP` signal to rclone for
 it to flush all directory caches, regardless of how old they are.

docs/content/commands/rclone_serve_sftp.md

@@ -1,5 +1,5 @@
 ---
-date: 2020-02-10T14:50:44Z
+date: 2020-02-10T14:59:49Z
 title: "rclone serve sftp"
 slug: rclone_serve_sftp
 url: /commands/rclone_serve_sftp/
@@ -49,7 +49,9 @@ Using the `--dir-cache-time` flag, you can set how long a
 directory should be considered up to date and not refreshed from the
 backend. Changes made locally in the mount may appear immediately or
 invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires.
+be picked up once the cache expires if the backend configured does not
+support polling for changes. If the backend supports polling, changes
+will be picked up on within the polling interval.
 
 Alternatively, you can send a `SIGHUP` signal to rclone for
 it to flush all directory caches, regardless of how old they are.

docs/content/commands/rclone_serve_webdav.md

@@ -1,5 +1,5 @@
 ---
-date: 2020-02-10T14:50:44Z
+date: 2020-02-10T14:59:49Z
 title: "rclone serve webdav"
 slug: rclone_serve_webdav
 url: /commands/rclone_serve_webdav/
@@ -95,7 +95,9 @@ Using the `--dir-cache-time` flag, you can set how long a
 directory should be considered up to date and not refreshed from the
 backend. Changes made locally in the mount may appear immediately or
 invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires.
+be picked up once the cache expires if the backend configured does not
+support polling for changes. If the backend supports polling, changes
+will be picked up on within the polling interval.
 
 Alternatively, you can send a `SIGHUP` signal to rclone for
 it to flush all directory caches, regardless of how old they are.

vfs/help.go

@@ -9,7 +9,9 @@ Using the ` + "`--dir-cache-time`" + ` flag, you can set how long a
 directory should be considered up to date and not refreshed from the
 backend. Changes made locally in the mount may appear immediately or
 invalidate the cache. However, changes done on the remote will only
-be picked up once the cache expires.
+be picked up once the cache expires if the backend configured does not
+support polling for changes. If the backend supports polling, changes
+will be picked up on within the polling interval.
 
 Alternatively, you can send a ` + "`SIGHUP`" + ` signal to rclone for
 it to flush all directory caches, regardless of how old they are.