summaryrefslogtreecommitdiff
path: root/system/loggedfs/README
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2017-03-24 17:22:07 +0000
committerDavid Spencer <idlemoor@slackbuilds.org>2017-03-25 00:07:32 +0000
commite0e452be7a5fb0b23519441af3c4d60c6dd18a03 (patch)
tree658f907c472162b11b14e495d4cf5aced70f77c1 /system/loggedfs/README
parent7588ac1bcec05944e2c93b54ab2cec7c2ea79b39 (diff)
downloadslackbuilds-e0e452be7a5fb0b23519441af3c4d60c6dd18a03.tar.gz
system/loggedfs: Added (filesystem monitoring with FUSE).
Signed-off-by: David Spencer <idlemoor@slackbuilds.org>
Diffstat (limited to 'system/loggedfs/README')
-rw-r--r--system/loggedfs/README16
1 files changed, 16 insertions, 0 deletions
diff --git a/system/loggedfs/README b/system/loggedfs/README
new file mode 100644
index 0000000000..829d936be5
--- /dev/null
+++ b/system/loggedfs/README
@@ -0,0 +1,16 @@
+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 let the real filesystem do the rest of the job.
+
+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.