From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29333 invoked by alias); 28 Feb 2002 15:30:46 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Received: (qmail 29206 invoked from network); 28 Feb 2002 15:30:32 -0000 Received: from unknown (HELO uhura.concentric.net) (206.173.118.93) by sources.redhat.com with SMTP; 28 Feb 2002 15:30:32 -0000 Received: from cliff.concentric.net (cliff.concentric.net [206.173.118.90]) by uhura.concentric.net [Concentric SMTP Routing 1.0] id g1SFUTB26445 ; Thu, 28 Feb 2002 10:30:30 -0500 (EST) Errors-To: Received: from Clemens.cris.com (da003d0325.sjc-ca.osd.concentric.net [64.1.1.70]) by cliff.concentric.net (8.9.1a) id KAA07055; Thu, 28 Feb 2002 10:30:27 -0500 (EST) Message-Id: <5.1.0.14.2.20020228072243.00aae918@pop3.cris.com> X-Sender: rrschulz@pop3.cris.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 28 Feb 2002 07:42:00 -0000 To: "Eugene Rosenzweig" , "Volker Quetschke" , From: Randall R Schulz Subject: Re: Child died with signal 13 In-Reply-To: <0c4401c1becc$a7cadbe0$0300a8c0@bluebox> References: <3C7B6591.9040503@scytek.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-SW-Source: 2002-02/txt/msg01393.txt.bz2 Eugene, Signal numbers and errno codes (and process status codes) are distinct. Process status codes to incorporate the signal number when a signal caused the death of the process. Signal 13 is SIGPIPE: Write to a pipe with no process there to read the data. In your context, this means the tar process has closed the pipe because it has concluded there is no more data to be retrieved from the gunzip sub-process it started in response to the 'z' option. If tar didn't do this, it would have to read all the gunzip-ed data. If it didn't either close the pipe (leading to the signal) or read the data, the child would just block and those processes would stall (at least until you or some other external action killed the tar + gunzip process group). Signal 2 is SIGINT, the signal that results when you type a ^C. Interactive shells suppress messages about certain signals causing process termination. In particular, SIGPIPE and SIGINT terminations are not reported as such by BASH. Tar is not making these exceptions. Randall Schulz Mountain View, CA USA At 05:51 2002-02-26, Eugene Rosenzweig wrote: >Hmm, it worked for me. I assume out of the documentation that tar will >spawn gzip -d filename and pipe it into itself. So, if 13 is the system >error from tar, which is EACCES, permission denied so maybe there is a >problem accessing the file? The listing shows that file is owned by >Administ(rator?) and prompt says Administrator so it seems correct but if >you substitute filename for nonexistent one then you get tar: Child died >with signal 2 <-- 2 being 'file not found' error so it seems that there is >a problem with permissions? > >Eugene. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/