I thought we were talking about poll interval and just removing poll interval.
You mean vfs-cache-mode full? That uses space on disk for reading and writing of files.
indeed yes, if I remove vfs-cache-mode full, will I have such fast access only with rclone rc vfs / refresh recursive = true --timeout 30m ??
currently like that the reading of a file starts at 3 seconds
My mount command creates a static mount, like @Animosity022 explained. It's read-only, and changes don't get polled. This works for me, because I only upload once a day, and never through the mount.
Since your use case is different, I would suggest you stick mostly with defaults. If you want to use the actual cache, and start times are faster, then by all means use it. Drop the refresh command in this case.
In this scenario, running the refresh command on the already running mount would then update the content and reflect the changes. After that, the mount goes back to being static. Does that make sense?
Indeed in this way the content put in the cloud seems available almost instantly on the emby server and the cache only takes up a very small amount of disk space, so far it seems to be the best way to go. 
rclone mount Gsuite: X: --cache-dir=C:\rclone\cache --vfs-cache-mode full --vfs-cache-max-size 100G --user-agent="ams"
timeout /t 60
C:\rclone\rclone rc vfs/refresh recursive=true --timeout 30m
I see errors in my command prompts like this:
vfs cache: failed to download: vfs reader: failed to write to cache file: read tcp 192.168.1.87:63159->152.217.13.202:443: i / o timeout.
or like this:
vfs cache: failed to _ensure cache vfs reader: failed to write to cache file: open file failed: Get "https://www.googleapis.com/drive/v3/files/1KkCy9BLAnOXkIQHQVujq2QTWdWlMgWYL?alt=media": dial tcp: lookup www.googleapis.com: no such host.
I don't know if this is preventing files from being read or if it was just the cloud that crashed. But I still have them often
Those are local network connectivity/DNS issues meaning you can't connect to Google from your machine.
If i click on https link a see this message:
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "dailyLimitExceededUnreg",
"message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.",
"extendedHelp": "https://code.google.com/apis/console"
}
],
"code": 403,
"message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."
}
}
It's like I said above, by rebuilding my libraries, according to me I have almost reached my limit of possible requests per day.
The message you initially shared is a network connectivity error not a limit error.
This means your local system tried to connect to the API and it failed to resolve the name as it got 'no such host'.
The error message in link is a separate issue related to your credentials expiring and that also needs to be solved.
It's curious i never had this problem, I think I only had to add the vpn dns in my card my network card
Thank you
Hi guys, i'm grappling with a new problem, and i'm wondering if rclone might be involved. Let me explain, I have migrated to linux ubuntu, I am able to run the mount, but emby does not see the mount folder once it is launched. So I can't point my libraries. I gave all access to my / mnt folder yet ...
thanks!
are you using --allow-other?
if that does not work, then post the command.
It's good only --allow-other was missing in the launch line 
Now that I'm going to do everything on the same machine, what would be the best linux launch line?
what does that mean?
what we talked about in this post was about it, but under windows
really, not sure what you mean?
a rclone mount command to run on linux?
exactly!!
Thanks 
i use this one: rclone mount --allow-other --vfs-cache-mode full Gcrypt: /mnt/cryption --user-agent="ams"
i shared a link with suggested settings,
homescripts/rclone.service at master · animosity22/homescripts · GitHub