[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: Pending patches
From:       Denys Vlasenko <vda.linux () googlemail ! com>
Date:       2008-10-31 23:33:29
Message-ID: 200811010033.30006.vda.linux () googlemail ! com
[Download RAW message or body]

On Friday 31 October 2008 11:56, Rob Landley wrote:
> Just having _files_ open prevents umounting a mount without -f:
>
> sudo /bin/bash
> mkdir walrus
> mount -t ramfs walrus walrus
> touch walrus/walrus
> sleep 999 < walrus/walrus
> umount walrus
> 
> A process has a file open in it.  The filesystem is pinned until the process 
> closes that file, unless you want to force the unmount (so the file starts 
> getting a -ESOMETHINGOROTHER).

This is not a problem.
killall5 -KILL closes a lot of open files.

Loop devices are worse because they interfere
even after one kills off all processes.

> > We do it not from process 1 but from it's children anyway.
> > Not much difference.
> 
> So instead of signaling PID 1 to do the work, you signal PID 1 to stop 
> respawning processes and have some other script do it.

Yes. Or I have something else respawning processes, not init.
It's easier to deal with it if you can kill it.
--
vda
_______________________________________________
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]