Just a general comment on "tar got signal 13".

On Mon, Oct 18, 2004 at 10:47:05AM +0200, Iulian Topliceanu wrote:
> Hi,
> 
...
> 
> Why do I get that '/bin/tar got signal 13'?
> 

Signal 13 is a "broken pipe" and generates
the error called "EPIPE", an error in a pipeline.

It is the system telling a process that the
process it is communicating with it is writing
to has terminated.

  EPIPE
    Broken pipe

    A write on a pipe for which there is no process to
    read the data.  This condition normally generates a
    signal;


For example in a three part pipeline:

  A | B | C

If process B dies, normally or abnormally process C will
simply drain whatever data is in the pipe and see an EOF
(end of file/end of data).  In contrast, if process A
continues to write into the its pipe to the dead process B,
it will receive the "broken pipe" signal.

The point of my comment is that your problem is unlikely
to be with tar, it is process A in my example.  Find out
why process B (or even something after B causing a chain
reaction) died before tar was done.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)