buffering SIGIO instances

From: Madhav (madhav.kelkar_at_gmail.com)
Date: 06/28/05 

Date: 28 Jun 2005 05:58:41 -0700

Hi all,

           I am using the signal based model for reading data from a
socket.
That is, i am using fcntl() to raise a SIGIO whenever there is data to
be read from that socket. I want to know if i get many instances of
SIGIO ( ie could be raised by calling write() multiple times on the
socket descriptor ) are they buffered by default?
            If they are not buffered, Is there any way to put the
signal on hold and later process it when i am inside a signal handler?

  Thanks in advance for your help.

Madhav.

Relevant Pages

  • buffering SIGIO instances
    ... i am using fcntlto raise a SIGIO whenever there is data to ... be read from that socket. ... signal on hold and later process it when i am inside a signal handler? ...
    (comp.unix.programmer)
  • buffering SIGIO instances
    ... i am using fcntlto raise a SIGIO whenever there is data to ... be read from that socket. ... signal on hold and later process it when i am inside a signal handler? ...
    (comp.os.linux.development.system)
  • Re: SIGIO question
    ... I presume that this is the same as for a socket or pipe. ... >get another SIGIO immediately after my read, ... when monitoring large numbers of file descriptors. ...
    (comp.unix.programmer)
  • Re: Realtime SIGIO signals questions (linux)
    ... i checked the socket code, and it does remove the process from the list when close is called, so that's not something u should be worried about. ... >> causing a SIGIO to be queued. ... >> same descriptor as the one I just closed. ... >> realtime signals a go. ...
    (comp.unix.programmer)
  • Re: buffering SIGIO instances
    ... i am using fcntl() to raise a SIGIO whenever there is data to ... > be read from that socket. ... signals are queued. ...
    (comp.os.linux.development.apps)