lazy unmount
This commit is contained in:
parent
d7b9ea2ee5
commit
8d7f84ac8e
2 changed files with 3 additions and 3 deletions
|
@ -30,5 +30,5 @@ executing the previous command will do the following
|
||||||
|
|
||||||
enabling the service file will mount the config on next user login
|
enabling the service file will mount the config on next user login
|
||||||
|
|
||||||
# Issues
|
# Notes
|
||||||
while technically supported, it's not possible to change or unmount a changeset once mounted. this is because the mount will become immediately busy, preventing `fusermount` from being able to unmount it.
|
when unmounting or changing a configuration changeset, the target mountpoint will be *lazily* unmounted. there is no guarantee when the volume will be successfully unmount. that said, it should be safe enough to remount a new configuration immediately after.
|
||||||
|
|
|
@ -33,7 +33,7 @@ if [ ! -d "$UPPER_DIR" ]; then
|
||||||
fi
|
fi
|
||||||
|
|
||||||
if [ "$2" == "unmount" ]; then
|
if [ "$2" == "unmount" ]; then
|
||||||
fusermount -u "$MOUNT_POINT"
|
fusermount -zu "$MOUNT_POINT"
|
||||||
echo "Unmounted $MOUNT_POINT"
|
echo "Unmounted $MOUNT_POINT"
|
||||||
exit 0
|
exit 0
|
||||||
fi
|
fi
|
||||||
|
|
Loading…
Add table
Reference in a new issue