Article View: comp.unix
Article #497Re: Pipes Signals Interprocess-I/O
From: Andrew Klossner
Date: Thu, 14 Jan 1988 15:23
Date: Thu, 14 Jan 1988 15:23
16 lines
1034 bytes
1034 bytes
[These answers apply to Berkeley-derived Unices ...]
"Well, the SIGIO handler works fine to detect input from places
like stdin, but never sees anything coming down the pipe."
The man page for fcntl(2) says that SIGIO only happens for
terminal-class files.
"Is there a way that I can determine WHICH file descriptor
caused a SIGIO interrupt to be invoked?"
Not directly, but you can find out at any time which fd's have input
ready with select(2).
--
-=- Andrew Klossner (decvax!tektronix!tekecs!andrew) [UUCP]
(andrew%tekecs.tek.com@relay.cs.net) [ARPA]
Technical Details
Message-ID:
<3426@mcdchg.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!rutgers!uwvax!oddjob!hao!noao!mcdsun!mcdchg!usenetReferences:
<2951@mcdchg.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!rutgers!uwvax!oddjob!hao!noao!mcdsun!mcdchg!usenet From: andrew@frip.gwd.tek.com (Andrew Klossner) Newsgroups: comp.unix Subject: Re: Pipes Signals Interprocess-I/O Message-ID: <3426@mcdchg.UUCP> Date: 14 Jan 88 15:23:42 GMT References: <2951@mcdchg.UUCP> Sender: usenet@mcdchg.UUCP Organization: Tektronix, Wilsonville, Oregon Lines: 16 Approved: usenet@mcdchg.UUCP