Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!brunix!iris.brown.edu!jhc
From: jhc@iris.brown.edu (James H. Coombs)
Newsgroups: comp.unix.questions
Subject: RE: interrupt driven sockets
Message-ID: <30852@brunix.UUCP>
Date: 27 Feb 90 18:29:34 GMT
References: <4597@rouge.usl.edu>
Sender: news@brunix.UUCP
Distribution: usa
Organization: IRIS
Lines: 17

In article <4597@rouge.usl.edu> pcb@gator.cacs.usl.edu (Peter C. Bahrs) 
writes:
> It is my understanding that if an interrupt occurs, some system calls
> will return and error (i.e. -1 for read, write, accept,...).  This means
> that ?EVERY? system call must be checked

Some system calls restart automatically.  In general, you need to check and
restart only for "slow" devices, such as terminals and sockets.  Have to 
run---
check the man page for sigvec() and trace from there.

--Jim

Dr. James H. Coombs
Senior Software Engineer, Research
Institute for Research in Information and Scholarship
Box 1946, Brown University, Providence, RI 02912