> >
> > Why can't you just enable sigio on the reply socket, send all the
> > requests with a 0 timeout and then wait for a signal to either
> > interrupt the sending or to notify you when you complete sending?
> >
> > Your solution seems awfully complex for what seems to be a simple
> > problem
* Alfred Perlstein <[EMAIL PROTECTED]> [010326 19:57] wrote:
> * Bill Paul <[EMAIL PROTECTED]> [010326 16:05] wrote:
>
> Why can't you just enable sigio on the reply socket, send all the
> requests with a 0 timeout and then wait for a signal to either
> interrupt the sending or to notify you when
* Bill Paul <[EMAIL PROTECTED]> [010326 16:05] wrote:
> Ok. Friday I sat down and tried to make the -m option to ypbind work
> correctly using the new TI-RPC code. Unfortunately, my test machine
> chose that day to eat itself. Even more unfortunately, it was an AMD
> 900Mhz Thunderbird. Today, I s
Ok. Friday I sat down and tried to make the -m option to ypbind work
correctly using the new TI-RPC code. Unfortunately, my test machine
chose that day to eat itself. Even more unfortunately, it was an AMD
900Mhz Thunderbird. Today, I started working on another box and managed
to get things to wor
