home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.perl
- Path: sparky!uunet!munnari.oz.au!cs.mu.OZ.AU!nareen.acci.COM.AU!ggr
- From: ggr@nareen.acci.COM.AU (Greg Rose)
- Subject: Re: timing problem with $SIG{'CHLD'}
- Message-ID: <9234910.11586@mulga.cs.mu.OZ.AU>
- Sender: news@cs.mu.OZ.AU
- Organization: Australian Computing and Communications Institute
- References: <1992Dec9.102933.27264@hemlock.cray.com> <9=h2hs#@rpi.edu>
- Date: Sun, 13 Dec 1992 23:56:32 GMT
- Lines: 22
-
- In article <9=h2hs#@rpi.edu> nobled@rebecca.its.rpi.edu (David Noble) writes:
- > until ($addr = accept(NS,S))
- > { die $! unless $! eq 'Interrupted system call'; }
- >
- >Of course, this breaks if the text of the error message varies for
- >different platforms. In that case, you would have to check for any
- >variants on the interrupted system call message. Anybody know offhand
- >whether the text of $! is defined by perl or the operating system?
-
- My understanding is that the text of the error message comes from
- somthing that (eg. IBM) vendors often change, but the *NUMBER*
- associated with the error is defined by POSIX. So I always use
-
- sub EINTR { 4; }
-
- until ($addr = accept(NS,S)) {
- die $! unless $! == &EINTR;
- }
- --
- Greg Rose Australian Computing and Communications Institute
- ggr@acci.com.au +61 18 174 842
- `Use of the standard phrase "HIJACKED" may be inadvisable' -- CAA
-