[lmi-commits] [lmi] master e0ab3def: Improve a recommended workaround

[Greg Chicares]

branch: master
commit e0ab3def1d8bc567b99799bbe57935bfde4f26cc
Author: Gregory W. Chicares <gchicares@sbcglobal.net>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Improve a recommended workaround
    
    Replaced a dangerous copy-pastable command to kill all schroot sessions
    with a safer suggestion. Added a 'umount -l' suggestion, which appears
    to have become necessary with the latest 'schroot' version.
---
 lmi_setup_02.sh | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/lmi_setup_02.sh b/lmi_setup_02.sh
index 49871807..18c896f0 100755
--- a/lmi_setup_02.sh
+++ b/lmi_setup_02.sh
@@ -71,10 +71,18 @@ findmnt -ro SOURCE,TARGET \
   | sed -e's,^[/A-Za-z0-9_-]*[[]\([^]]*\)[]],\1,' \
   | column -t
 
-# If the next command fails due to unwanted dormant sessions, then
+# If the next command fails due to an unwanted dormant session, then
 # a command such as
-#   sudo schroot -e -c `schroot -l --all-sessions`
-# may be used to terminate them.
+#   sudo schroot -e -c session:[name of session]
+# may be used to terminate it. If that fails with
+#   E: 10mount: umount: /run/schroot/mount/[name of session]: target is busy.
+#   E: 10mount: rmdir: failed to remove '/var/run/schroot/mount/[...]:
+#      Device or resource busy
+# then
+#   sudo umount -l /run/schroot/mount/[name of session]
+# may be necessary, where '-f' for "force" would seem too severe, and
+# '-l' for "lazy" seems sufficient.
+
 findmnt | grep "${CHRTNAME}" && exit 9
 
 # Use '--one-file-system' because it was designed for this use case: