On Thu, 13 Jul 2000, Michael Borrelli wrote:
> Richard B. Johnson said this...
> >This came up about a year ago. From what I remember, it was determined
> >that pipes are not supposed to generate signals when data are available
> >because you can't even write to a pip
ent found it yet.
> > Any comments from the linux-kernel folks ?
> > /gat
> > anyway i'd still like to see that small sample that u say fails this.
>
> This came up about a year ago. From what I remember, it was determined
> that pipes are not supposed to generate sig
Richard B. Johnson said this...
>This came up about a year ago. From what I remember, it was determined
>that pipes are not supposed to generate signals when data are available
>because you can't even write to a pipe unless you have a reader already
>reading. Basically, the pip
termined
that pipes are not supposed to generate signals when data are available
because you can't even write to a pipe unless you have a reader already
reading. Basically, the pipe will block on a write until somebody
reads it and a reader will block until somebody writes. Attempts to
set the pipes
a SIGIO while Solaris issues a
> SIGPOLL - these all work as documented. Under Linux, something
> isn't right. The man page for fcntl says I should get a SIGIO when
> I/O is possible, but I don't.
>
> If you're really "up" on these Linux signals, and would like
---
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Vladislav
> Grinchenko
> Sent: Wednesday, July 12, 2000 8:22 AM
> To: [EMAIL PROTECTED]
> Subject: Re: SIGIO signals not generated in Redhat 6.2?
>
>
> Matt Marlow wrote:
>
> > Hi, I've been
Matt Marlow wrote:
> Hi, I've been working on a program that is supposed to generate
> a SIGIO signal whenever there is a read or write on a certain
> file descriptor. Yet it seems no matter what I do (short of a
> "kill( SIGIO, getpid() )") I cannot get a SIGIO generated under
> Redhat 6.2!
Mat
the man for fcntl a dozen times...have used F_SETOWN
and F_SETFL to setup the expected SIGIO, have enabled a handler
for SIGIO via sigaction, etc. Running "strace -f -e trace=signal"
I get a listing of all the program signals, but never see a
SIGIO when stuff is written to/read from the fi
Grrr This confuses me. Can you please help me define some terminology
and clear things up?
1) In regards to signals, if a signal is BLOCKED, what does that mean?
2) If a signal is IGNORED, that means that it is not CAUGHT, right?
3) If I fill a signal set with all signals and that to the
