From: urgrue <urgrue@bulbous.org>
To: linux-admin@vger.kernel.org
Subject: "resume" cp/mv
Date: Mon, 06 Feb 2006 17:28:06 +0200 [thread overview]
Message-ID: <43E76B06.50201@bulbous.org> (raw)
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.
next reply other threads:[~2006-02-06 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 15:28 urgrue [this message]
2006-02-06 15:40 ` "resume" cp/mv Thornton Prime
2006-02-06 15:42 ` Tim Walberg
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=43E76B06.50201@bulbous.org \
--to=urgrue@bulbous.org \
--cc=linux-admin@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.