From de108d3fc06dd9de404c497dfa9faa26956f43e3 Mon Sep 17 00:00:00 2001
From: Jakob Unterwurzacher
Date: Sat, 2 Jan 2021 18:11:18 +0100
Subject: -idle: don't lazy-unmount

When a process has its working dir inside the mount,
the only way we notice is that we get EBUSY when trying
to unmount.

We used to lazy-unmount in this case, but this means
pulling the rug from under the process.

For example, bash will start throwing

  cd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

messages.

Fixes https://github.com/rfjakob/gocryptfs/issues/533
---
 Documentation/MANPAGE.md | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'Documentation/MANPAGE.md')

diff --git a/Documentation/MANPAGE.md b/Documentation/MANPAGE.md
index a984aa6..5febe90 100644
--- a/Documentation/MANPAGE.md
+++ b/Documentation/MANPAGE.md
@@ -241,6 +241,9 @@ Only for forward mode: automatically unmount the filesystem if it has been idle
 for the specified duration. Durations can be specified like "500s" or "2h45m".
 0 (the default) means stay mounted indefinitely.
 
+When a process has open files or its working directory in the mount,
+this will keep it not idle indefinitely.
+
 #### -kernel_cache
 Enable the kernel_cache option of the FUSE filesystem, see fuse(8) for details.
 
-- 
cgit v1.2.3