scp: Problem when source and destination are identical

[Chris Adams]

Once upon a time, Markus Friedl <markus.friedl at informatik.uni-erlangen.de> said:
> On Wed, May 23, 2001 at 11:23:52PM +0200, Gert Doering wrote:
> > On Wed, May 23, 2001 at 03:07:28PM -0500, Jim Knoble wrote:
> > > What i would much rather see is for the destination scp to write the
> > > incoming file to a temporary file in the same directory, and then
> > > rename() it to the destination file on a successful copy.
> > 
> > Strongly seconded.  But Markus doesn't seem to like it, for no other
> > reason than "you can use tar/mv/rsync to do this".
> 
> no, the reason is: scp == rcp

If scp == rcp and rcp can handle this case, shouldn't scp?

Has anyone looked at the BSD rcp source to see how it is handled there?
-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.