Why does it say `deleting is not possible: no permission` when actually the problem is that another process is using the directory? [closed]
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
Why is reported as "permission" error when I try to do
sudo rm -rf directory
while some other process (e.g. another shell) has directory
as its working directory?
"directory
is in use by process ..." would be the much more helpful error message in this case don't you agree?!
ubuntu permissions rm delete
closed as unclear what you're asking by RalfFriedl, muru, mdpc, Goro, Romeo Ninov Sep 26 at 5:55
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, itâÂÂs hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
-1
down vote
favorite
Why is reported as "permission" error when I try to do
sudo rm -rf directory
while some other process (e.g. another shell) has directory
as its working directory?
"directory
is in use by process ..." would be the much more helpful error message in this case don't you agree?!
ubuntu permissions rm delete
closed as unclear what you're asking by RalfFriedl, muru, mdpc, Goro, Romeo Ninov Sep 26 at 5:55
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, itâÂÂs hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
4
I have no problems deleting a directory in use by another process.
â muru
Sep 25 at 17:56
Maybe there are other things that would cause the same error. Helpful or misleading?
â xenoid
Sep 25 at 19:39
There is an EBUSY error code. What type of filesystem is this directory on? It's possible that the filesystem driver doesn't know the right error to return. If you're using WSL, it may not be possible for the Unix side to find out which win32 process has the directory locked.
â Mark Plotnick
Sep 25 at 20:32
That is not what happens on Linux when one removes the working directory of another shell process. unix.stackexchange.com/questions/434417
â JdeBP
Sep 25 at 23:00
add a comment |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
Why is reported as "permission" error when I try to do
sudo rm -rf directory
while some other process (e.g. another shell) has directory
as its working directory?
"directory
is in use by process ..." would be the much more helpful error message in this case don't you agree?!
ubuntu permissions rm delete
Why is reported as "permission" error when I try to do
sudo rm -rf directory
while some other process (e.g. another shell) has directory
as its working directory?
"directory
is in use by process ..." would be the much more helpful error message in this case don't you agree?!
ubuntu permissions rm delete
ubuntu permissions rm delete
asked Sep 25 at 17:53
masterxilo
992
992
closed as unclear what you're asking by RalfFriedl, muru, mdpc, Goro, Romeo Ninov Sep 26 at 5:55
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, itâÂÂs hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by RalfFriedl, muru, mdpc, Goro, Romeo Ninov Sep 26 at 5:55
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, itâÂÂs hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
4
I have no problems deleting a directory in use by another process.
â muru
Sep 25 at 17:56
Maybe there are other things that would cause the same error. Helpful or misleading?
â xenoid
Sep 25 at 19:39
There is an EBUSY error code. What type of filesystem is this directory on? It's possible that the filesystem driver doesn't know the right error to return. If you're using WSL, it may not be possible for the Unix side to find out which win32 process has the directory locked.
â Mark Plotnick
Sep 25 at 20:32
That is not what happens on Linux when one removes the working directory of another shell process. unix.stackexchange.com/questions/434417
â JdeBP
Sep 25 at 23:00
add a comment |Â
4
I have no problems deleting a directory in use by another process.
â muru
Sep 25 at 17:56
Maybe there are other things that would cause the same error. Helpful or misleading?
â xenoid
Sep 25 at 19:39
There is an EBUSY error code. What type of filesystem is this directory on? It's possible that the filesystem driver doesn't know the right error to return. If you're using WSL, it may not be possible for the Unix side to find out which win32 process has the directory locked.
â Mark Plotnick
Sep 25 at 20:32
That is not what happens on Linux when one removes the working directory of another shell process. unix.stackexchange.com/questions/434417
â JdeBP
Sep 25 at 23:00
4
4
I have no problems deleting a directory in use by another process.
â muru
Sep 25 at 17:56
I have no problems deleting a directory in use by another process.
â muru
Sep 25 at 17:56
Maybe there are other things that would cause the same error. Helpful or misleading?
â xenoid
Sep 25 at 19:39
Maybe there are other things that would cause the same error. Helpful or misleading?
â xenoid
Sep 25 at 19:39
There is an EBUSY error code. What type of filesystem is this directory on? It's possible that the filesystem driver doesn't know the right error to return. If you're using WSL, it may not be possible for the Unix side to find out which win32 process has the directory locked.
â Mark Plotnick
Sep 25 at 20:32
There is an EBUSY error code. What type of filesystem is this directory on? It's possible that the filesystem driver doesn't know the right error to return. If you're using WSL, it may not be possible for the Unix side to find out which win32 process has the directory locked.
â Mark Plotnick
Sep 25 at 20:32
That is not what happens on Linux when one removes the working directory of another shell process. unix.stackexchange.com/questions/434417
â JdeBP
Sep 25 at 23:00
That is not what happens on Linux when one removes the working directory of another shell process. unix.stackexchange.com/questions/434417
â JdeBP
Sep 25 at 23:00
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
4
I have no problems deleting a directory in use by another process.
â muru
Sep 25 at 17:56
Maybe there are other things that would cause the same error. Helpful or misleading?
â xenoid
Sep 25 at 19:39
There is an EBUSY error code. What type of filesystem is this directory on? It's possible that the filesystem driver doesn't know the right error to return. If you're using WSL, it may not be possible for the Unix side to find out which win32 process has the directory locked.
â Mark Plotnick
Sep 25 at 20:32
That is not what happens on Linux when one removes the working directory of another shell process. unix.stackexchange.com/questions/434417
â JdeBP
Sep 25 at 23:00