>>>>> "ML" == Marc Lehmann <[EMAIL PROTECTED]> writes:
ML> Solaris can tell you which event caused the signal, so there is no
ML> need to scan your list of operations. After all, that's the point
ML> of sigio.
please quote the docs that show this. according to my solaris 7 docs,
you have to call aio_wait to get an aio_result back. this can be one of
several pending and so you have to scan your list of aio_result
structures. you allocate them and pass one into the aio_read/write
call and that is returned by the aio_wait call. it is the same design as
with sigchild. the signal tell you nothing but something happened and
you have to call wait* to get the pid and exit code of the child. that
has to be then used to find the control structure of the process if you
are managing them like that.
there is no method for the signal mechanism that i see that tell you
which handle is available to read/write.
also show me the exact man pages in linux which has similar features as
solaris aio support. i have not found any.
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
