Return to BSD News archive
Xref: sserve comp.unix.bsd:13785 comp.unix.sys5.r4:7126 Newsgroups: comp.unix.bsd,comp.unix.sys5.r4 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!csn!slate!mbarkah From: mbarkah@slate.mines.colorado.edu (Ade Barkah) Subject: Re: Asynchronous I/O Message-ID: <1994Apr28.221452.61954@slate.mines.colorado.edu> Date: Thu, 28 Apr 1994 22:14:52 GMT Distribution: usa References: <2ov4ov$gg4@news.hal.COM> <1994Apr28.154047.4957@njitgw.njit.edu> Organization: Colorado School of Mines X-Newsreader: TIN [version 1.2 PL1] Followup-To: comp.unix.bsd,comp.unix.sys5.r4 Lines: 16 Katz (dileep@earth.njit.edu) wrote: : I would like to be informed asynchronously about a file : descriptor being ready for reading. ... : Strangely, the handler is invoked for the input activity just once. : Never after that. In SysV environments the signal handler is reset after it is invoked. The solution is to simply set the signal handler (signal()) again after the signal is raised, usually in the signal handling routine. -Ade