From owner-freebsd-bugs  Thu Apr 20 17:05:05 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id RAA14555
          for bugs-outgoing; Thu, 20 Apr 1995 17:05:05 -0700
Received: from localhost (localhost [127.0.0.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA14547
          ; Thu, 20 Apr 1995 17:05:02 -0700
X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol
To: rw@namu01.gwdg.de (Rainer Wittmann UMS)
cc: bugs@FreeBSD.org
Subject: Re: signal handling bug 
In-reply-to: Your message of "Thu, 20 Apr 95 14:50:45 +0200."
             <9504201250.AA26059@namu01.gwdg.de> 
Date: Thu, 20 Apr 1995 17:05:00 -0700
Message-ID: <14542.798422700@freefall.cdrom.com>
From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

> Any unix system, I know, except FreeBSD 2.0, behaves as follows,
> if a process is reading from a slow device like standard input from
> a terminal. If this process receives a signal, for which a signal
> handler was installed by the process, then immediately control
> is tranferred to the signal handler (FreeBSD does this as well).
> After the signal was serviced, the read system call is termianted
> and errno is set to EINTR. Rather then doing this, FreeBSD completes
> the read system call, as if no signal would have arrived. This

I believe this is standard BSD behavior, if my past reading of the
emacs sources are correct.  Are you sure that the UNIX systems
you've used up to now weren't SYSV based?  This bit of SYSV
brainda^H^H^H^H^H^Hbehavior is well documented..

					Jordan