in reply to Re^2: Random script crashes related to File::Copy (care)
in thread Random script crashes related to File::Copy

Hence, I believe the problem is somehow timing related rather than the actual command structure. If the problem was really related to "Invalid cross-device link" errors or the like, would that not then cause the script to crash every time

Not all. After all, "Text file busy" means *something else* (another handle? another process?) is keeping the file "busy" (mmapped?).

  • Comment on Re^3: Random script crashes related to File::Copy (care)

Replies are listed 'Best First'.
Re^4: Random script crashes related to File::Copy (care)
by tye (Sage) on Apr 29, 2009 at 23:59 UTC

    Your response appears to be a result of a faulty parsing of English. "If X, then would crash every time" vs "Not every time, because Y could be timing related". While "X" is "not Y".

    - tye        

      I can't makes sense of your sentence fragments. I read

      If the problem was really related to "Invalid cross-device link" errors or the like, would that not then cause the script to crash every time

      as

      If the problem was really related to "Invalid cross-device link" errors or the like, I would expect the script to crash every time the error is encountered. Isn't that so?

      and I interpreted "or the like" to mean "or other errors in the displayed strace". Is that wrong?