Extra copy options
Dave Higton (281) 668 posts |
I’d like to see two more copy options, to help make backup operations more reliable: 1) Automatic retry of failed operations; 2) Failed (or retried and failed) operations to be logged and the copy continue uninterrupted. Where the log should be is open to debate; the most obvious to me are a TaskWindow or Syslog. If you try a backup of 70k-ish objects to NAS, you’ll understand why both of the above are important. |
André Timmermans (100) 655 posts |
There is another option I’d like to see: ask for confirmation only when overwriting an existing file. I guess though that it would be more useful on the filer_action side where you could eventually display both files attributes (size, file type and time stamp). |
Steve Revill (20) 1361 posts |
I’d like to have an option which causes an OS_UpCall 6 after each object is copied. I hate big *copy operations causing a machine to single task even when run in a task window. I usually end up doing the (lumpy) -v to work around this because I think each newline in the output causes an UpCall 6 to be generated but then of course you have an ever-filling task window full of the verbose output… not good, especially if the copy operation was part of some process you’re running in a task obey file with specific (important) bits of output that you don’t want drowning in waffle. |