From 896ce0639a476158141a5f1f7d72a62e54432259 Mon Sep 17 00:00:00 2001 From: "B. Watson" Date: Thu, 27 Apr 2023 22:35:34 +0100 Subject: system/loggedfs: Added (filesystem monitoring with FUSE) Signed-off-by: bedlam Signed-off-by: Willy Sudiarto Raharjo --- system/loggedfs/README | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 system/loggedfs/README (limited to 'system/loggedfs/README') 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. -- cgit v1.2.3