Use real path on DB content and program path, exactly:
1. On caller program path - always
2. On file associated with operation path - only on open operation
This will remove problem with configuration
RealPath is C standard library call: man realpath (3).
We probably cannot use this approach on files inside storage. FUSE do not return context information probably, when our daemon access mount point. It does not give context in other cases too, so there is no way to test if our daemon do some stuff (and skip some steps in this case).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Realpath on program path done. We must also create programs group and group programs path with symlinks inside directories consists by PATH. We can iterate on each files inside directories pointed by PATH and monitor directories pointed by PATH thanks to inotify/fanotify.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We probably cannot use this approach on files inside storage. FUSE do not return context information probably, when our daemon access mount point. It does not give context in other cases too, so there is no way to test if our daemon do some stuff (and skip some steps in this case).
Realpath on program path done. We must also create programs group and group programs path with symlinks inside directories consists by PATH. We can iterate on each files inside directories pointed by PATH and monitor directories pointed by PATH thanks to inotify/fanotify.