fsnotify VS juicefs

Like monitored_rsync, gofs use the fsnotify module to monitor file changes, and use inotify under linux.

https://github.com/fsnotify/fsnotify (may not be supported in unraid with the overlay fs)

You may want to check out https://github.com/fsnotify/fsnotify and see how they handle it.

i don't use org-agenda but i was looking at you code and you may want to use fsnotify instead of a timer that may use more CPU than it should:

I think you can try fsnotify altrough you will need Go do build the cmd part. Once built you can attach it folder and pipe output to other command.

See https://github.com/fsnotify/fsnotify/issues/413

https://github.com/gobuffalo/buffalo/issues/510 https://github.com/fsnotify/fsnotify/issues/152

Why not one of the native Go file watching libs (e.g. fsnotify/notify/etc)? In general you're much more likely to get better control over behaviour from native code than from shelling out.

Support for Kerberos keytab files

JuiceFS under the Apache License 2.0, is a high-performance POSIX file system optimized for cloud-native environments. It stores data in Object Storage (e.g., Amazon S3) and metadata in databases like Redis, MySQL, or TiKV. JuiceFS integrates massive cloud storage with big data, machine learning, and AI applications efficiently, akin to local storage. It features full POSIX and Hadoop compatibility, S3 interface, Kubernetes support, and shared file storage for numerous clients. Some cool features are - strong consistency, scalable performance, data encryption, global file locks, and compression with LZ4 or Zstandard.

To improve the handling process of capacity overrun, the JuiceFS client supports deletion operations in the case of Ceph cluster fullness (see related code changes in JuiceFS Community Edition). Therefore, for newer client versions, there is no need to use set-full-ratio for temporary adjustments.

If you have any questions or would like to learn more, feel free to join discussions about JuiceFS on GitHub and the JuiceFS community on Slack.

The architecture image shows GCS and others, so I suspect it does.

https://github.com/juicedata/juicefs#architecture

See also: JuiceFS: https://juicefs.com/

Adds a DBMS or key-value store for metadata, making the filesystem much faster (POSIX, small overwrites don't have to replace a full object in the GCS/S3 backend).

Almost certainly a better solution if you want to turn your object storage into a mountable filesystem, with the (big) caveat that you can't access the files directly in the bucket (they are not stored transparently).

JuiceFS can do the same thing as s3fs-fuse, but better. Because it supports robust data consistency and caching policies to improve performance.