From: rick.jones2@hp.com   
      
   Dan Lanciani  wrote:   
   > In article , rick.jones2@hp.com (Rick   
   Jones) writes:   
   > | > > Yes.  getsockopt(...SO_ERROR...) is not going to do what you want.   
   > |   
   > | > so why is it there?   
   > | > What type of Information does it yield?   
   > |   
   > | If I were to guess, it might relate, at least in part, to the "errfds"   
   > | parm of select().   
      
   > But select() doesn't have an errfds parameter. :)   
      
   Well, the HP-UX 11 manpage calls it errorfds :)   
      
         int select(int nfds, fd_set *__restrict readfds,   
              fd_set *__restrict writefds, fd_set *__restrict errorfds   
              struct timeval *__restrict timeout);   
      
   rick jones   
   --   
   I don't interest myself in "why." I think more often in terms of   
   "when," sometimes "where;" always "how much."  - Joubert   
   these opinions are mine, all mine; HP might not want them anyway... :)   
   feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)