filePro Utility Menu - Rename a file

[John Esak]

> No, we performed this task in the evening when no one was on the system.
> We
> did check the system to see if anyone was on remotely.


Yes, but there could have been a hung process handed over to PID 1 that
continued *after* everyone logged out.  If this was the case, your "remove"
command would not be visible until it could get a hold of the file. This
obviously happened when you shut down and all processes are killed
regardless. Well, the obviously refers to what happens when you shut down...
maybe something else caused this strange behavior, but I think Ken is right,
something had use of this file or a part of it and the rm couldn't fully do
its work.

If you want to see this happen again, try this.

Edit a file called /tmp/junk. Save the file out. Then go back into the file
with vi.  On another login *while* the first login is vi'ing the file
/tmp/junk, cd to /tmp and do a listing of junk. You will see it there. Then
remove the file with "rm junk". Do a listing and it will be gone. You think
it is removed... *but* the other login still has it and is using it. Go back
to the first login and work in the file with vi. For that process it still
exists and *is* there. When you save the file out, however, the rm command
from the other login will promtply remove it.

I believe some process was working with that file when you rm'd it. It's a
very possible explanation.

John