Dan Christensen wrote: > > Is there an easy way to determine what makes a filesystem busy, e.g. > what prevents me from remounting /usr readonly after an upgrade? > Usually some file that was erased is being held open by a process, > but I don't know an easy way to determine which file or process. > "lsof | grep usr" is a start, but provides too long a list. Is > there an easier way? >
I think 'fuser' would work for you. From the manpage -- fuser displays the PIDs of processes using the specified files or file systems. In the default display mode, each file name is followed by a letter denoting the type of access: hth, kent
