It seems it is an issue with the BusyBox implementation of PRoot in the app I am using (UserLand).
https://github.com/CypherpunkArmory/UserLAnd/issues/110 Thanks everyone for your help! - I will have to wait for UserLand to fix the problem. Mark On Mon, Sep 10, 2018 at 1:01 PM, James Bowlin <[email protected]> wrote: > On Mon, Sep 10, 2018 at 11:49 AM, Mark Phillips said: > > Thanks for the reference. I found that early in my search for a > > solution, and tried it with no success. Apologies for not > > including it in my original post. > > The Google search for the error message had many other hits (30 > million). I think your problem is related to one of those and is > not a separate issue due to a bug in busybox. The system is > telling the busybox rm, rmdir commands that the directory is not > empty and the path forward is to figure out why. One solution > was to check the file attributes with lsattr. Another was to > check and fix the file system. Yet another was related to a > process that was using a file in the directory. > > > HTH, James >
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
