home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky biz.sco.general:4776 comp.unix.sysv386:17571
- Path: sparky!uunet!shady!kevin
- From: kevin@shady.UUCP (Kevin Smith)
- Newsgroups: biz.sco.general,comp.unix.sysv386
- Subject: Re: sigaction() and rescheduling interrupted system calls
- Keywords: sigaction system call sco reschedule
- Message-ID: <64@shady.UUCP>
- Date: 21 Dec 92 08:16:25 GMT
- References: <1992Dec16.100827.10097@dd.dk>
- Followup-To: biz.sco.general
- Organization: ShadeTree Software, Inc.
- Lines: 31
-
- In article <1992Dec16.100827.10097@dd.dk> wes@dd.dk (Mads Westermann) writes:
- :>I'm running SCO ODT 2.0 (SCO Unix 3.2.4) and have run into the problem
- :>of rescheduling an interrupted system call after a signal has occured.
- :>
- :>In my AT&T Sys V.4 manual there's reference to a SA_RESTART flag on
- :>the sigaction() function that causes interrupted system calls to be
- :>transparently restarted.
- :>
- :>In my Ultrix 4.2 manual there's reference to a SV_INTERRUPT flag that
- :>does the same.
- :>
- :>My SCO manual doesn't know of any such thing - It seems like the only
- :>possibility is to manually check the return code and the errno from the
- :>system call and manually restart the system-call if errno equals EINTR.
- :>
- :>Has anybody solved the problem ? Is there a way to solve it ?
- :>
- :>Any input on this subject would be greatly appreciated.
- :>
-
- Since most system calls are not interruptable the problem is not as big as
- it might seem. Terminal and printer I/O, pause(), wait(), messages and
- semiphores are about it (and probably any network/socket read and writes)
- Ok so there are a few. Your basic disk and tape IO are, however, not
- interruptable so the interrupt actually occurs immediatly after the system
- call.
- --
- | Email - !shady!kevin uunet!shady!kevin kevin%shady@uunet.uu.net
- Kevin Smith | Voice - (908) 874-7980
- | Mail - ShadeTree Software, Inc., 192 Capricorn Dr. #10,
- | Somerville, NJ 08876
-