<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Error EWOULDBLOCK in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/error-ewouldblock/m-p/2688877#M54928</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I would like to know which version of s700_800 11.00 cumulative ARPA Transport patch you have on your system.&lt;BR /&gt;&lt;BR /&gt;I believe there was an issue with this and is resolved as from patch PHNE_17662&lt;BR /&gt;&lt;BR /&gt;C.</description>
    <pubDate>Fri, 22 Mar 2002 08:01:21 GMT</pubDate>
    <dc:creator>Clemens van Everdingen</dc:creator>
    <dc:date>2002-03-22T08:01:21Z</dc:date>
    <item>
      <title>Error EWOULDBLOCK</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-ewouldblock/m-p/2688876#M54927</link>
      <description>When using send() to write data in a socket, the error EWOULDBLOCK appears if there is no space in the system to buffer any of the data.&lt;BR /&gt;&lt;BR /&gt;Is it possible, by configuration of the kernel or something else, to increase the size of the buffer, to reduce the occurrence of this error.&lt;BR /&gt;&lt;BR /&gt;Michel</description>
      <pubDate>Fri, 22 Mar 2002 07:34:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-ewouldblock/m-p/2688876#M54927</guid>
      <dc:creator>Jolivet</dc:creator>
      <dc:date>2002-03-22T07:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: Error EWOULDBLOCK</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-ewouldblock/m-p/2688877#M54928</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I would like to know which version of s700_800 11.00 cumulative ARPA Transport patch you have on your system.&lt;BR /&gt;&lt;BR /&gt;I believe there was an issue with this and is resolved as from patch PHNE_17662&lt;BR /&gt;&lt;BR /&gt;C.</description>
      <pubDate>Fri, 22 Mar 2002 08:01:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-ewouldblock/m-p/2688877#M54928</guid>
      <dc:creator>Clemens van Everdingen</dc:creator>
      <dc:date>2002-03-22T08:01:21Z</dc:date>
    </item>
    <item>
      <title>Re: Error EWOULDBLOCK</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-ewouldblock/m-p/2688878#M54929</link>
      <description>You can increase it up to 256k inside the application by calling setsockopt() as follows:&lt;BR /&gt;&lt;BR /&gt;int qsize = 262140, arglen = sizeof(int);&lt;BR /&gt;setsockopt(socket, SOL_SOCKET, SO_SNDBUF, &amp;amp;qsize, arglen);&lt;BR /&gt;&lt;BR /&gt;You'll want to check the return code is not -1 in case this fails for some reason.   Man setsockopt for more details.&lt;BR /&gt;&lt;BR /&gt;Note that no matter how high you set the buffer size you're still going to get hit with the EWOULDBLOCK error, this is perfectly normal when using non-blocking sockets.  You have to code your application to handle this condition.  The best way is to use select() to tell you when the socket is ready to send to.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Steve</description>
      <pubDate>Fri, 22 Mar 2002 09:33:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-ewouldblock/m-p/2688878#M54929</guid>
      <dc:creator>Steven Gillard_2</dc:creator>
      <dc:date>2002-03-22T09:33:25Z</dc:date>
    </item>
  </channel>
</rss>

