Date: Tue, 22 Aug 2000 23:15:56 -0700 From: "Crist J . Clark" <cjclark@reflexnet.net> To: Mike Andrews <mandrews@bit0.com> Cc: freebsd-security@FreeBSD.ORG Subject: Re: scp and >2GB files Message-ID: <20000822231556.J28027@149.211.6.64.reflexcom.com> In-Reply-To: <Pine.BSF.4.21.0008230130340.62647-100000@mindcrime.bit0.com>; from mandrews@bit0.com on Wed, Aug 23, 2000 at 01:36:46AM -0400 References: <Pine.BSF.4.21.0008230130340.62647-100000@mindcrime.bit0.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 23, 2000 at 01:36:46AM -0400, Mike Andrews wrote: > Any plans to improve scp so it can copy files larger than 2^31 bytes? For > those that haven't tried it, scp dies with "lost connection" almost > immediately after authenticating. (I'm guessing it's seeing the file size > as a negative number and getting confused.) > > It would make a disk-to-disk backup solution I'm working on much easier. > With scp not able to do this easily, I'm not sure what I can use as a > quick replacement - maybe dump/restore to stdout run over an ssh pipeline, > or maybe rdist. I've run tar over an ssh pipeline, but tar doesn't like > files over 2^31 bytes either... > > This is OpenSSH on 4.1-RELEASE, btw. Isn't, $ scp file1 remote:file2 Same as, $ ssh remote 'cat > file2' < file1 But prolly doesn't have that limit. -- Crist J. Clark cjclark@alum.mit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000822231556.J28027>