From owner-freebsd-arch Thu Mar 7 14:44:47 2002 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 392DC37B417 for ; Thu, 7 Mar 2002 14:44:36 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g27MiGnK005180; Thu, 7 Mar 2002 23:44:16 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: arch@FreeBSD.ORG Subject: Re: Contemplating THIS change to signals. (fwd) In-Reply-To: Your message of "Thu, 07 Mar 2002 14:37:17 PST." Date: Thu, 07 Mar 2002 23:44:16 +0100 Message-ID: <5179.1015541056@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Ju lian Elischer writes: >My suggestion is to stop making STOP type signals an exception, >because it should not be necessary to stop them in the middle of a >syscall, just stop them from getting back to userspace. I don't agree: we can have very long running syscalls, and being able to stop them may make sense sendfile(), RAID5-rebuilds etc etc. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message