linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Walberg <twalberg@mindspring.com>
To: urgrue <urgrue@bulbous.org>
Cc: linux-admin@vger.kernel.org
Subject: Re: "resume" cp/mv
Date: Mon, 6 Feb 2006 09:42:59 -0600	[thread overview]
Message-ID: <20060206154259.GD2481@mindspring.com> (raw)
In-Reply-To: <43E76B06.50201@bulbous.org>

Sounds like a good match for rsync...


On 02/06/2006 17:28 +0200, urgrue wrote:
>>	Anyone know of any trick to make mv/cp support some form of crash-recovery?
>>	
>>	The problem is, if I'm moving a huge directory/file, and the transfer 
>>	fails, there is absolutely no way to continue where I left off. This is 
>>	awfully primitive.
>>	
>>	The only way I can think of is to zssh into my own localhost and use 
>>	rz/sz, or the same via ftp, but this seems like a pathetic kludge, and 
>>	even those dont work very well with large directories full of files.
>>	-
>>	To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>>	the body of a message to majordomo@vger.kernel.org
>>	More majordomo info at  http://vger.kernel.org/majordomo-info.html
End of included message



-- 
+--------------------------+------------------------------+
| Tim Walberg              | twalberg@mindspring.com      |
| 830 Carriage Dr.         | www.mindspring.com/~twalberg |
| Algonquin, IL 60102      |                              |
+--------------------------+------------------------------+

  parent reply	other threads:[~2006-02-06 15:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 15:28 "resume" cp/mv urgrue
2006-02-06 15:40 ` Thornton Prime
2006-02-06 15:42 ` Tim Walberg [this message]
2006-02-06 15:46 ` Scott Taylor
2006-02-06 15:57 ` hansel
2006-02-07  7:28   ` Prosenjit Kundu
2006-02-07 15:50     ` urgrue
2006-02-08  6:07       ` Jeff Woods

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060206154259.GD2481@mindspring.com \
    --to=twalberg@mindspring.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=urgrue@bulbous.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).