Re: aio_read() oddness

On Wednesday 06 March 2002 07:03, Tony Arcieri wrote: I'm not currently subscribed to this list, so please cc replies to me. I was playing around with aio_read() and ran into some seemingly aberrant behavior, although not with aio_read() itself, but the resulting signal. Within struct aiocb

Re: aio_read() oddness

FreeBSD does not support queued signals (part of RT Posix) which is required for this. -Kip = For RAIDANT status see: http://cranford.eng.netapp.com:8080/cgi-bin/ant4/index.cgi To submit

Re: aio_read() oddness

Note: Please cc replies to me as I'm not currently subscribed. Kip Macy [EMAIL PROTECTED] wrote: FreeBSD does not support queued signals (part of RT Posix) which is required for this. -Kip I guess I'll have to take a look at kqueues then. On a similar note,

Re: aio_read() oddness

I'd asked myself the same thing. In code that uses it I have to do an #ifdef FreeBSD. My guess was that it was because it is more conformant with the structure name and no one of consequence noticed because the underlying functionality is not really there. -Kip

aio_read() oddness

I'm not currently subscribed to this list, so please cc replies to me. I was playing around with aio_read() and ran into some seemingly aberrant behavior, although not with aio_read() itself, but the resulting signal. Within struct aiocb I was setting: aio_sigevent.sigev_notify = SIGEV_SIGNAL;