bug in scp (OpenSSH)

[Erik Benner]

I like the command line option to turn it off, or better yet a compile
option to toggle the default and a command line to toggle as well. Should
the toggle be for the bar or the throughput update?


-----Original Message-----
From: owner-openssh-unix-dev at mindrot.org
[mailto:owner-openssh-unix-dev at mindrot.org]On Behalf Of Dave Dykstra
Sent: Wednesday, September 05, 2001 5:05 PM
To: Jason Stone
Cc: openssh-unix-dev at mindrot.org
Subject: Re: bug in scp (OpenSSH)


On Tue, Sep 04, 2001 at 04:37:59PM -0700, Jason Stone wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> > >This has come up many times before, and the consensus of the developers
> > >seems to be that they're not interested in fixing or adding features to
> > >scp because they want to make scp just the secure version of rcp, and
it's
> > >not up to them to change rcp.
> >
> > One thing I have missing from other versions is the throughput meter
> > in the status bar.
>
> Incidentally, at my last company, the progress bar was a source of
> breakage for legacy scripts that didn't expect rcp to be producing any
> output - so what's up with that?  How does that fit into your model of
> being rsh/rcp compatible and not introducing extraneous features?  Do you
> really think that breaking rcp compatibility with a status bar is a better
> idea than "breaking" it with, for example, a flag to allow atomic
> transfers?
>
> Don't you think that if the progress bar exists at all, it should at least
> be enabled via commandline option or environment variable, and not be the
> default?


I agree.  At least with ssh 1.2.27 there was a configure option to disable
it, --disable-scp-stats.  Showing those statistics by default are not in
the Unix spirit.  At least it won't show them if stderr is not a tty.

- Dave Dykstra