On 12/16/11 13:21, Joachim Schmitz wrote: > The standalone version works just fine.
That's too bad. I'm afraid there's no magic here: we need to see what system calls are being executed by 'rm', and in what order, and what arguments they are being given, and what their results are, so that we can figure out what's going wrong. Since NonStop doesn't have 'truss', I guess you'll need to put a breakpoint on every system call and see what its arguments are and what it returns, starting with the system call that opens the directory. Or, you can put wrappers around each system call in the source code, and have the wrappers send diagnostics to stderr.
