public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Oliver Neukum <oliver@neukum.org>,
	luto@myrealbox.com, aebr@win.tue.nl,
	linux-kernel@vger.kernel.org
Subject: Re: the umount() saga for regular linux desktop users
Date: Sun, 2 Jan 2005 22:05:36 +0100	[thread overview]
Message-ID: <20050102210536.GF4183@stusta.de> (raw)
In-Reply-To: <20050102205650.GG18136@elf.ucw.cz>

On Sun, Jan 02, 2005 at 09:56:50PM +0100, Pavel Machek wrote:
> 
> Okay, so the right solution is probably something more like
> 
> while umount /mnt; do
> 	fuser -km -TERM /mnt
> 	sleep 1
> 	fuser -km /mnt
> done
> 
> Not sure how many command line users can do this... Perhaps including
> fumount script doing this is good idea?

A command line user only needs to know about fuser, and in the unlikely 
case if the race condition Oliver thought of occurs he'll note since 
umount will give an error message.

I'd even say the more common case is to use fuser to get the PIDs of the 
processes and manually check which they are - e.g. you might not want to 
kill your OpenOffice with many open documents only because you'd 
forgotten that it still has one document open on the file system you are 
trying to remove.

> 								Pavel

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-01-02 21:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02 19:37 the umount() saga for regular linux desktop users Pavel Machek
2005-01-02 20:11 ` Adrian Bunk
2005-01-02 20:15   ` Pavel Machek
2005-01-02 20:34   ` Oliver Neukum
2005-01-02 20:51     ` Adrian Bunk
2005-01-02 20:56       ` Pavel Machek
2005-01-02 21:05         ` Adrian Bunk [this message]
2005-01-03  9:35           ` Frank van Maarseveen
2005-01-03 19:14             ` Ingo Oeser
2005-01-02 20:36   ` Adrian Bunk
2005-01-03  1:36     ` Puneet Vyas
2005-01-02 20:36   ` Andreas Schwab
     [not found] <fa.foeqpaf.nlmd9n@ifi.uio.no>
     [not found] ` <fa.d9avdr3.1jm46gr@ifi.uio.no>
2005-01-03  1:17   ` Bodo Eggert
     [not found] <fa.iji5lco.m6nrs@ifi.uio.no>
     [not found] ` <fa.fv0gsro.143iuho@ifi.uio.no>
2005-01-02 12:38   ` Bodo Eggert
2005-01-02 20:27     ` Adrian Bunk
2005-01-03  0:37       ` Bodo Eggert
2005-01-02 22:43     ` Valdis.Kletnieks
2005-01-04 20:28       ` Lee Revell
2005-01-05  2:12         ` Bodo Eggert
  -- strict thread matches above, loose matches on Subject: below --
2004-12-31 17:41 William
2004-12-31 17:47 ` Arjan van de Ven
2004-12-31 17:48 ` Ush
2004-12-31 18:22   ` Gene Heskett
2004-12-31 18:31     ` Miquel van Smoorenburg
2004-12-31 21:48     ` Tom Felker
2005-01-01  0:07       ` Gene Heskett
2004-12-31 17:50 ` Andries Brouwer
2005-01-01 19:40   ` Andy Lutomirski
2004-12-31 17:51 ` Gene Heskett
2005-01-16  4:39 ` Greg Stark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050102210536.GF4183@stusta.de \
    --to=bunk@stusta.de \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@myrealbox.com \
    --cc=oliver@neukum.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox