Tell me more ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

When I copy multiple files on a Mac, the system tries to copy them all at the same time. The problem is two-fold.

First of all, when you select multiple files and copy them, they all go into one process with an "all or nothing" approach not unlike ACID in databases. Often this is not desireable.

Further, when you add other copy-processes, the system tries to copy everything at the same time.

For example, I decide to copy a large file A, then later I decide to copy a large file B as well. This results in two parallel copy operations, regardless if one of the "large files" also is a selection of many files.

I do not like this for several reasons:

  • When several copy processes run at once, it seems to bogs down other processes.
  • Also, when several files are copied at the same time, the copy process itself seems to go much slower.
  • And lastly, if the process is aborted, none of the files reach its destination.
  • When adding a file to the queue, it will also start copying at once, and bogging down the process even further.
  • This is a real problem when copying to other machines or drives on the (local) net.

Result: The file A, which I wanted to transfer and use first, takes much longer to arrive than needed, and when copying from a central HD on the LAN, I cannot use the first file until all the other files also have arrived.

Thus... How do I queue multiple files for copying on a Mac? To clarify: Regardless of many files are chosen, or they are added one by one, I want them all put into a queue that only copies one file at a time, until the queue is done.

Answers in Bash and especially Perl are also welcome!

share|improve this question
I really don't understand the question. It partly seems you start multiple independent copy operations at once, and then again, you don't...? Have you tried copying all relevant files as part of the same copy operation e.g. by selecting them all, then dragging to the destination; or selecting them, Cmd-C, then Cmd-V at the destination? – Daniel Beck Aug 27 '11 at 13:57
@Daniel I tried to clarify the question — this is a problem I've encountered myself as well: It's about starting independent copy operations. The solution would be a queue where you can just put files to be copied and the jobs would be processed in a sequential way. – slhck Aug 27 '11 at 14:01
@slhck How does And lastly, if the process is aborted, none of the files reach its destination apply to independent operations? What does I cannot use the first file until all the other files also have arrived. mean? – Daniel Beck Aug 27 '11 at 14:02
It's also a problem when selecting many files and copying them. All the files constitute one process where the files in it aren't possible to queue. This is IMHO also bad. Nevertheless, I'd also like to add files to a queue. – Kebman Aug 27 '11 at 15:22
They are actually copied one after the other. You mean the order in which they're copied is essentially random? – Daniel Beck Aug 27 '11 at 16:05

4 Answers

up vote 4 down vote accepted

UltraCopier

UltraCopier is a free and cross-platform copy utility that is currently in development, so it's not that neat and polished yet. Once you install it, it sits in your menu bar.

It manages a copy list that allows you to queue copy or move jobs, which are then sequentially processed. You can also define the copy process priority as well as the block size of the transfer.

With the new version you can group with similar source and/or destination, or just always or never.

enter image description here

share|improve this answer
Nice! Using! Works perfect! Actually looked up XCode, Cocoa and Objective C contemplating writing my own app. – Kebman Aug 27 '11 at 17:10

Here is a bash solution:

cp file1 dest1; cp file2 dest2

Repeat this for how ever many files you want to copy. Just keep adding semicolons and cp commands.

You could also do

cp file1 dest1 && cp file2 dest2

In this example, the file will only be copied if the one before it copied successfully.

For a folder, you can do something like this:

for x in folder/*; do echo "Copying $x"; cp "$x" destdir; done
share|improve this answer
But when you try to copy an entire folder this way, it is treated as one process again, which isn't desirable. I also want each file in the folder queued. – Kebman Aug 27 '11 at 15:28
@Kebman: See my most recent edit. – Wuffers Aug 27 '11 at 15:31
1  
Be aware of files with spaces and globbing characters with the for approach. I'd probably do it with a find -print0 piped into xargs -0 to be safe. – slhck Aug 27 '11 at 15:50

Path Finder 6 looks easier to navigate than ultracopier and definitely creates a clear cue, plus it has way more options. There's also a 30 day trial for it.

But I'm using this professionally so I say totally worth it.

File Operations in Path Finder 6 (YouTube video)

share|improve this answer

This answer will hopefully become relevant in the future.

The Finder alternative Path Finder will include a basic copy queue functionality in the next major release. It's the most up voted feature request.

A basic single-window copy queue will be included in Path Finder 6.

Unfortunately, as of May 2011, there's no known release date.

We have no current time estimate, but we recently brought in a second programmer so work progress a bit more quickly.

share|improve this answer
Path Finder 6 is out – does it have the feature? – slhck Jul 19 '12 at 12:30

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.