Joost Claessen [EMAIL PROTECTED] writes:
On Mon, May 29, 2000 at 09:47:44PM +, ktb wrote:
I don't know if it would work or even be recommended but have you tried
the -k option to kill all processes to that file system? The other
thought I had is boot into your system as a single user
On Mon, May 29, 2000 at 10:10:12PM -0400, 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
On Mon, May 29, 2000 at 09:47:44PM +, ktb wrote:
I don't know if it would work or even be recommended but have you tried
the -k option to kill all processes to that file system? The other
thought I had is boot into your system as a single user but I'm sure
that is what your trying to
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
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.
On Mon, 29 May 2000, Dan Christensen [EMAIL PROTECTED] 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
Christophe TROESTLER [EMAIL PROTECTED] writes:
On Mon, 29 May 2000, Dan Christensen [EMAIL PROTECTED] 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
Dan Christensen wrote:
Christophe TROESTLER [EMAIL PROTECTED] writes:
On Mon, 29 May 2000, Dan Christensen [EMAIL PROTECTED] 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
8 matches
Mail list logo
