From owner-freebsd-questions Sun Mar 4 17:23:41 2001 Delivered-To: freebsd-questions@freebsd.org Received: from smtpf.casema.net (smtpf.casema.net [195.96.96.173]) by hub.freebsd.org (Postfix) with SMTP id 79B8D37B719 for ; Sun, 4 Mar 2001 17:23:38 -0800 (PST) (envelope-from walter@binity.com) Received: (qmail 3974 invoked by uid 0); 5 Mar 2001 01:23:35 -0000 Received: from unknown (HELO slash.b118.binity.net) (195.96.105.172) by smtpf.casema.net with SMTP; 5 Mar 2001 01:23:35 -0000 Received: from tsunami.b118.binity.net (tsunami.b118.binity.net [172.18.3.10]) by slash.b118.binity.net (Postfix) with ESMTP id 8BADB10F for ; Mon, 5 Mar 2001 02:22:59 +0100 (CET) Date: Mon, 5 Mar 2001 02:24:56 +0100 From: Walter Hop X-Mailer: The Bat! (v1.49) Educational X-Priority: 3 (Normal) Message-ID: <139127338372.20010305022456@binity.com> To: FreeBSD Questions Subject: tar just doesn't want to be KILLed Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi *, am I right in assuming that... 1. there's no way to get rid of an instance of tar (that's probably waiting for some IO to complete? 2. there's no way to umount a mount point held by such a process? [If so, I would be interested to hear about the design considerations that led to this! I guess that tar never returns from a syscall and can't react to the signal? Hasn't anybody tried to implement a workaround for this in all those years?] Thanks! walter -- The more aggressively you search for the most profound experience of your life, the more rigid, narrowing, dispiriting and routine it becomes. -- Matthew Klam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message