The timeout in seconds for which file attributes are cached for the purpose of checking if auto_cache should flush the file data on open.
The timeout in seconds for which file/directory attributes (as returned by e.g. the getattr handler) are cached.
This option is an alternative to kernel_cache. Instead of unconditionally keeping cached data, the cached data is invalidated on open(2) if if the modification time or the size of the file has changed since it was last opened.
This option disables the use of page cache (file content cache) in the kernel for this filesystem. This has several affects:
The timeout in seconds for which name lookups will be cached.
The default behavior is that if an open file is deleted, the file is renamed to a hidden file (.fuse_hiddenXXX), and only removed when the file is finally released. This relieves the filesystem implementation of having to deal with this problem. This option disables the hiding behavior, and files are removed immediately in an unlink operation (or in a rename operation which overwrites an existing file).
Allow requests to be interrupted
Specify which signal number to send to the filesystem when a request is interrupted. The default is hardcoded to USR1.
This option disables flushing the cache of the file contents on every open(2). This should only be enabled on filesystems where the file data is never changed externally (not through the mounted FUSE filesystem). Thus it is not suitable for network filesystems and other intermediate filesystems.
The timeout in seconds for which a negative lookup will be cached. This means, that if file did not exist (lookup returned ENOENT), the lookup will only be redone after the timeout, and the file/directory will be assumed to not exist until then. A value of zero means that negative lookups are not cached.
If this option is given the file-system handlers for the following operations will not receive path information: read, write, flush, release, fallocate, fsync, readdir, releasedir, fsyncdir, lock, ioctl and poll.
If use_ino option is not given, still try to fill in the d_ino field in readdir(2). If the name was previously looked up, and is still in the cache, the inode number found there will be used. Otherwise it will be set to -1. If use_ino option is given, this option is ignored.
Normally, FUSE assigns inodes to paths only for as long as the kernel is aware of them. With this option inodes are instead remembered for at least this many seconds. This will require more memory, but may be necessary when using applications that make use of inode numbers.
If set_gid is non-zero, the st_gid attribute of each file is overwritten with the value of gid.
If set_mode is non-zero, the any permissions bits set in umask are unset in the st_mode attribute of each file.
If set_uid is non-zero, the st_uid attribute of each file is overwritten with the value of uid.
The remaining options are used by libfuse internally and should not be touched.
Honor the st_ino field in the functions getattr() and fill_dir(). This value is used to fill in the st_ino field in the stat(2), lstat(2), fstat(2) functions and the d_ino field in the readdir(2) function. The filesystem does not have to guarantee uniqueness, however some applications rely on this value being unique for the whole filesystem.
Configuration of the high-level API.