Er, could it possibly be that telnet has been hiding the error
all along? It's really, really hard to see how ssh could
*create* this sort of error.
Barney Wolff
On Sun, Feb 11, 2001 at 09:35:43AM +0100, Blaz Zupan wrote:
> > pkg_add runs tar with the --fast-read option to extract the table of
> > contents. When I remove the option pkg_add no longer reports broken
> > pipes. When gunzip'ing piped to tar, and tar exits early due to
> > the option, gunzip properly gets a 'gzip: stdout: Broken pipe' error.
> >
> > Maybe 'tar' was changed recently, maybe 'gunzip' was changed recently,
> > I don't know. But it isn't a kernel problem. The kernel is doing
> > exactly what it is supposed to be doing.
>
> A simple "cvs diff" between RELENG_4_2_0_RELEASE and RELENG_4 reveals, that
> gzip has not changed at all, while tar has only grown bzip2 support.
>
> As Kent suggests, ssh might be the problem. To verify, I have just logged in
> through telnet and done a "pkg_add gmake-3.79.1.tgz". And yes indeed, the
> broken pipe message disappears.
>
> So the OpenSSH 2.3.0 seems to be causing the problem.
>
> Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia
> E-mail: [EMAIL PROTECTED], Tel: +386-2-320-6320, Fax: +386-2-320-6325
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
