libgocryptfs/internal/fusefrontend
Jesse Dunietz 87d3ed9187 Add option for autounmount
Even though filesystem notifications aren't implemented for FUSE, I decided to
try my hand at implementing the autounmount feature (#128). I based it on the
EncFS autounmount code, which records filesystem accesses and checks every X
seconds whether it's idled long enough to unmount.

I've tested the feature locally, but I haven't added any tests for this flag.
I also haven't worked with Go before. So please let me know if there's
anything that should be done differently.

One particular concern: I worked from the assumption that the open files table
is unique per-filesystem. If that's not true, I'll need to add an open file
count and associated lock to the Filesystem type instead.

https://github.com/rfjakob/gocryptfs/pull/265
2018-10-11 20:16:45 +02:00
..
args.go reverse mode: add --exclude option 2018-08-11 23:26:49 +02:00
ctlsock_interface.go fusefrontend: implement path decryption via ctlsock 2017-05-07 21:01:39 +02:00
file_allocate_truncate.go fusefrontend: truncateGrowFile: pass zeroPad error to caller 2018-08-15 17:25:22 +02:00
file_holes.go fusefrontend: doWrite: delete file header if first write fails 2018-07-15 15:12:55 +02:00
file.go fusefronted: disallow writes running concurrently with reads 2018-07-22 22:29:22 +02:00
fs_dir.go fusefrontend: get rid of os.File* wrapping 2018-09-23 12:17:26 +02:00
fs.go Add option for autounmount 2018-10-11 20:16:45 +02:00
names.go Add option for autounmount 2018-10-11 20:16:45 +02:00
xattr_darwin.go xattr: added passing of a "flags" parameter 2018-05-07 21:45:40 +02:00
xattr_linux_unit_test.go Improved xattr handling on non-linux systems (#227) 2018-04-17 20:33:04 +02:00
xattr_linux.go xattr: added passing of a "flags" parameter 2018-05-07 21:45:40 +02:00
xattr_unit_test.go Improved xattr handling on non-linux systems (#227) 2018-04-17 20:33:04 +02:00
xattr.go fsck: rename "CorruptItems" channel to "MitigatedCorruptions" 2018-07-01 20:56:22 +02:00