aboutsummaryrefslogtreecommitdiff
path: root/system/loggedfs/README
diff options
context:
space:
mode:
authorB. Watson <urchlay@slackware.uk>2023-04-27 22:35:34 +0100
committerWilly Sudiarto Raharjo <willysr@slackbuilds.org>2023-04-29 18:11:37 +0700
commit896ce0639a476158141a5f1f7d72a62e54432259 (patch)
treeaf039bce6b57a2c03978ba590a1352a3bee60c3b /system/loggedfs/README
parentd3a015d4c6d7f8d52e6dea676ed419903988a283 (diff)
system/loggedfs: Added (filesystem monitoring with FUSE)
Signed-off-by: bedlam <dave@slackbuilds.org> Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'system/loggedfs/README')
-rw-r--r--system/loggedfs/README21
1 files changed, 21 insertions, 0 deletions
diff --git a/system/loggedfs/README b/system/loggedfs/README
new file mode 100644
index 0000000000000..90617bc62f01d
--- /dev/null
+++ b/system/loggedfs/README
@@ -0,0 +1,21 @@
+loggedfs (filesystem monitoring with FUSE)
+
+LoggedFS is a fuse-based filesystem which can log every operation that
+happens in it. LoggedFS only sends a message to syslog (or a file)
+when called by fuse and then lets the real filesystem do the rest of
+the job.
+
+There is a sample config file installed as /etc/loggedfs.xml, for use
+with the -c option.
+
+Note: loggedfs doesn't cross filesystem boundaries. If you e.g. have
+/usr/local mounted as a separate partition, monitoring /usr won't
+also monitor /usr/local (though you can always run another instance of
+loggedfs in that case).
+
+Slackware note: since Slackware's /etc/mtab is a regular file (not
+a symlink to /proc/mounts), killing a loggedfs process causes its
+/etc/mtab entry to stay. This makes it look like the filesystem is
+still mounted, though it actually isn't. To avoid this, always use
+"fusermount -u" to cleanly umount the fs, which will also make the
+loggedfs process exit.