Date: Tue, 25 Feb 1997 09:55:34 +0000 From: joe@pavilion.net (Josef Karthauser) To: freebsd-stable@freebsd.org Cc: softweyr@xmission.com (Wes Peters) Subject: Re: gzip: stdout: Broken pipe Message-ID: <Mutt.19970225095534.joe@florence.pavilion.net> In-Reply-To: <199702201517.IAA00727@obie.softweyr.ml.org>; from Wes Peters on Feb 20, 1997 08:17:35 -0700 References: <Mutt.19970220122628.joe@florence.pavilion.net> <199702201517.IAA00727@obie.softweyr.ml.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Wes Peters writes: > Josef Karthauser writes: > > core# pkg_add ghostscript-2.6.2.tgz > > > > gzip: stdout: Broken pipe > > tar: child returned status 1 > > ^CTar extract of /tmp/ghostscript-2.6.2.tgz failed! > > Unable to extract `/tmp/ghostscript-2.6.2.tgz'! > > > > I'm not sure when they started. It seems to work properly from the > > serial console if I log on as root, but breaks if I su from an xterm. > > I'm running bash as my main shell, and root's is the default csh. > > You probably have a different TMPDIR in your account vs. root. Your > /tmp is filling up and gzip can't uncompress the file. Either 'su -' to > pick up root's TMPDIR setting or point TMPDIR at some filesystem with > more free space and try again. > Thanks for this, unfortunately it doesn't appear to be the cause. I've further tracked it down to something to do with tar with the 'z' flag. If I execute a 'tar -zxvf filename' I often get: gzip: stdout: Broken pipe tar: child returned status 1 Wierd... it's not to do with file space, I've got plenty. Here's my current enviroment: LOGNAME=joe VISUAL=ted TERMCAP=xterm|vs100|xterm terminal emulator (X window system):li#24:hs:ts=\E[?E\E[?%i%dT:fs=\E[?F:es:ds=\E[?E:is=\E>\E[?1;3;4;5l\E[?7;8h\E[1;65r\E[65;1H:rs=\E>\E[?1;3;4;5l\E[?7;8h:@7=\E[4~:kh=\E[1~:kI=\E[2~:k0=\E[10~:kD=\E[3~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:k;=\E[21~:F1=\E[23~:F2=\E[24~:kP=\E[5~:kN=\E[6~:K1=\EOw:K2=\EOy:K3=\EOu:K4=\EOq:K5=\EOs:al=\E[L:dl=\E[M:im=\E[4h:ei=\E[4l:mi:dc=\E[P:AL=\E[%dL:DL=\E[%dM:DC=\E[%dP:do=\E[B:cl=\E[H\E[J:sf=\ED:as=\E(0:ae=\E(B:cm=\E[%i%d;%dH:nd=\E[C:up=\E[A:nw=\EE:ce=\E[K:cd=\E[J:so=\E[7m:se=\E[m:us=\E[4m:ue=\E[m:md=\E[1m:mr=\E[7m:mb=\E[5m:me=\E[m:sr=\EM:sc=\E7:rc=\E8:cs=\E[%i%d;%dr:UP=\E[%dA:DO=\E[%dB:RI=\E[%dC:LE=\E[%dD:ct=\E[3g:st=\EH:co#80:le=^H:bs:am:if=/usr/share/tabset/vt100:ac=llmmkkjjuuttvvwwqqxxnnpprr``aa:ks=\E[?1h\E=:ke=\E[?1l\E>:ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:kb=\177:ho=\E[H:pt:vt#3:xn:ta=^I:ms:bl=^G:cr=^M:eo:it#8:ut: TERM=xterm HOSTTYPE=i386 PATH=~/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin:/usr/contrib/bin:/usr/X11R6/bin HOME=/home/joe SHELL=/usr/local/bin/bash MORE=-ce USER=joe BLOCKSIZE=1k SESSION_MANAGER=local/core.pavilion.net:/tmp/.ICE-unix/5507,tcp/core.pavilion.net:2981 DISPLAY=ncd01:0.0 OSTYPE=FreeBSD WINDOWID=33554445 SHLVL=1 EDITOR=ted _=/usr/bin/env I'm running from an NCD Xterminal and recently upgraded X to a more recent version, although I can't understand how that might effect this. This machine is running 2.1.7, and I didn't have any problems under 2.1.6 Can anyone shed some light on this? Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970225095534.joe>