From a9b0d6b5c655da96783851d5304c4d800d4e4553 Mon Sep 17 00:00:00 2001 From: Bill Nottingham Date: Mon, 7 Mar 2011 15:53:45 -0500 Subject: Don't do force/lazy umount for the first nfs umount. (#676851, ) This can cause hung tasks that aren't cleaned up or killed properly, as their dangling references won't get caught. --- rc.d/init.d/functions | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'rc.d') diff --git a/rc.d/init.d/functions b/rc.d/init.d/functions index 01cfed8c..ff6ac88c 100644 --- a/rc.d/init.d/functions +++ b/rc.d/init.d/functions @@ -124,7 +124,7 @@ __fgrep() { return 1 } -# __umount_loop awk_program fstab_file first_msg retry_msg umount_args +# __umount_loop awk_program fstab_file first_msg retry_msg retry_umount_args # awk_program should process fstab_file and return a list of fstab-encoded # paths; it doesn't have to handle comments in fstab_file. __umount_loop() { @@ -134,7 +134,7 @@ __umount_loop() { remaining=$(LC_ALL=C awk "/^#/ {next} $1" "$2" | sort -r) while [ -n "$remaining" -a "$retry" -gt 0 ]; do if [ "$retry" -eq 3 ]; then - action "$3" fstab-decode umount $5 $remaining + action "$3" fstab-decode umount '' $remaining else action "$4" fstab-decode umount $5 $remaining fi -- cgit v1.2.1