Actualy broken pipe can be caused by bzip2 or gzip exiting before tar. This can happen when all data has been decompressed in a pipe. the sigpipe signal is reported by Bash but is harmless unless an error proceeds it. Regards, Kerry. On Thu, Nov 28, 2002 at 07:10:15AM -0600, Adam Myrow wrote: > A broken pipe means one process finished before another. In this case, it > sounds like tar aborted before bzip2 could complete. There should have > been another message before the broken pipe. Are you low on memory by any > chance? Are your tar files more than 2GB? Those are the only things that > come to mind. > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- Kerry Hoath: kerry at gotss.net kerry at gotss.eu.org or kerry at gotss.spice.net.au ICQ: 8226547 msn: kerry at gotss.net Yahoo: kerryhoath at yahoo.com.au