Geoffrey Roberts
03/14/2023 4:54 PM
post122166
|
Hello,
For some years I have encountered the message "Resource Busy" when I try to copy an executable file to a name of one
that's currently running. This is often the case when I have modified a program and simply want to replace the one
that's running. It hasn't really been a problem - more of a nuisance but one that I could live with.
But recently, I have been getting this message when the file simply exists - regardless of whether it is running or not.
I have to remove the file (rm) before I can copy a new one over it. Although sometimes this doesn't occur more often
than not it does and I am somewhat confused by what is actually happening. I'm using the most recent release of 7.1 but
this message was apparent back in the 6.x days.
So my question is: what is the criteria that governs when this "Resource Busy" is issued requiring either the running
process to be stopped or the destination file to be removed?
I guess to date I have considered it to be simply one of life's little mystery's.
Geoff.
|
|
|