Date: Wed, 03 Apr 2002 18:03:44 -0800 From: vijay singh <vijay@IPRG.nokia.com> To: Peter Leftwich <Hostmaster@Video2Video.Com> Cc: FreeBSD Questions <FreeBSD-Questions@FreeBSD.Org> Subject: Re: gzip: stdout: Broken pipe Message-ID: <3CABB480.4B218472@iprg.nokia.com> References: <20020403201052.V68910-100000@earl-grey.cloud9.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi. The exact call made from a script run from cron, which looks for tgz
files and acts on them is
tar -xz --unlink -f ${tgz-file}
Should this be split into gunzip and tar?
thanks, vijay
Peter Leftwich wrote:
>
> On Wed, 3 Apr 2002, vijay singh wrote:
> > Hello, the gzip utility sometimes prints this message while uncompressing a tgz file. I found that this is really harmless, but is there is a fix for this available somewhere? Some scripts catch the return code and precess it as an error. I am using a 2.x based FreeBSD system. Kindly cc me in the reply.
> > br, vijay
>
> Why not use gunzip instead of gzip? Sometimes *.tgz files are confused by
> the OS as destined for *tape archives* and hence stdout gets confused as
> such!
>
> Can you repost with a "script" of what occurs when? (i.e. include your
> command line and the resulting errors as they appear)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CABB480.4B218472>