BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] rsync v. cp in data migration

Subject: [Discuss] rsync v. cp in data migration
From: richard.pieri at gmail.com (Richard Pieri)
Date: Fri, 24 May 2013 11:12:01 -0400
In-reply-to: <519EDF09.5050304@gmail.com>
References: <CANaytcdhtK6BF92OpHBt14MS0Z3U4YbnbM1dYxQdkvaVV7tXQQ@mail.gmail.com> <519E83F4.6050204@gmail.com> <519EB016.5010803@gmail.com> <519EDF09.5050304@gmail.com>

Tom Metro wrote:
> How about GNU cp, as found in Linux?

It's still file by file, or segment by segment, with the associated
buffer creation and teardown for each file copied. File by file is very
inefficient when copying files in bulk.

-- 
Rich P.

Follow-Ups:
- [Discuss] rsync v. cp in data migration
  - From: greg at freephile.com (Greg Rundlett (freephile))

References:
- [Discuss] rsync v. cp in data migration
  - From: greg at freephile.com (Greg Rundlett (freephile))
- [Discuss] rsync v. cp in data migration
  - From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] rsync v. cp in data migration
  - From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] rsync v. cp in data migration
  - From: tmetro+blu at gmail.com (Tom Metro)

Prev by Date: [Discuss] Discuss Digest, Vol 24, Issue 30
Next by Date: [Discuss] api? rest maybe?
Previous by thread: [Discuss] rsync v. cp in data migration
Next by thread: [Discuss] rsync v. cp in data migration
Index(es):
- Date
- Thread


BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Boston Linux & Unix / webmaster@blu.org