scp: Problem when source and destination are identical

[Gert Doering]

Hi,

On Thu, May 24, 2001 at 01:08:30PM +0200, Markus Friedl 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

Just because rcp has been implemented as "very unflexible" in the past
(I'd go so far and call it "broken"), does this mean we have to break 
scp as well?

We don't do the "use a separate TCP connection for stderr" thing from rsh
either, just because it's there...

(Yes, I can see your argument, "let's keep the source differences as small
as possible".  But hey, so let's fix it in rcp as well.).

gert

-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert.doering at physik.tu-muenchen.de