recv and MSG_WAITALL

Ask a Question related to UNIX Programming, Design and Development.

  1. #1

    Default Re: recv and MSG_WAITALL

    In article <82bf05fc.0307301943.14d7c7e@posting.google.com> ,
    Michael <msh@mindless.com> wrote:
    >I am trying to read a non-blocking socket using recv and MSG_WAITALL.
    >It does not seem to work under Solaris 8.
    >
    >Can anyone confirm this is the case, or is there some trick?
    If you want it to block, don't use a non-blocking socket.

    --
    Barry Margolin, [email]barry.margolin@level3.com[/email]
    Level(3), Woburn, MA
    *** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
    Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
    Barry Margolin Guest

  2. Similar Questions and Discussions

    1. High Recv-Q Netstat
      Hi, Could you tell me why when i trace using "netstat", I got queue Recv-Q very High? For information i was streaming to 500+ users concurrently...
    2. Pb with IO::Socket::INET and recv
      Hi all, Since I migrate a client program to Mandrake 9.1 (kernel 2.4.21-0.13) and perl 5.8.0, this little program didn't work. The problem occured...
    3. no recv
      "Paras Sharma" <parsharm@cisco.com> wrote in message news:3F0BE08E.2090601@cisco.com... You can try calling 'shutdown' to shutdown just the...
    4. Receive binary file through recv
      On 24 Jun 2003 15:19:11 -0700 michelle <theintangible1@hotmail.com> wrote: | Hi, I am trying to send a binary file from the client to the server....
  3. #2

    Default Re: recv and MSG_WAITALL


    "Barry Margolin" <barry.margolin@level3.com> wrote in message
    news:D6aWa.1$hu1.0@news.level3.com...
    > In article <82bf05fc.0307301943.14d7c7e@posting.google.com> ,
    > Michael <msh@mindless.com> wrote:
    > >I am trying to read a non-blocking socket using recv and MSG_WAITALL.
    > >It does not seem to work under Solaris 8.
    > >
    > >Can anyone confirm this is the case, or is there some trick?
    >
    > If you want it to block, don't use a non-blocking socket.
    Not to mention, if you're waiting for the other side to send more while
    the other side is waiting for you to receive to make buffer space available,
    you'll deadlock.

    DS


    David Schwartz Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139