- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error EWOULDBLOCK
Operating System - HP-UX
1819800
Members
3051
Online
109607
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-21-2002 11:34 PM
тАО03-21-2002 11:34 PM
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.
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.
Michel
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.
Michel
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2002 12:01 AM
тАО03-22-2002 12:01 AM
Re: Error EWOULDBLOCK
Hi,
I would like to know which version of s700_800 11.00 cumulative ARPA Transport patch you have on your system.
I believe there was an issue with this and is resolved as from patch PHNE_17662
C.
I would like to know which version of s700_800 11.00 cumulative ARPA Transport patch you have on your system.
I believe there was an issue with this and is resolved as from patch PHNE_17662
C.
The computer is a great invention, there are as many mistakes as ever, but they are nobody's fault !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2002 01:33 AM
тАО03-22-2002 01:33 AM
Solution
You can increase it up to 256k inside the application by calling setsockopt() as follows:
int qsize = 262140, arglen = sizeof(int);
setsockopt(socket, SOL_SOCKET, SO_SNDBUF, &qsize, arglen);
You'll want to check the return code is not -1 in case this fails for some reason. Man setsockopt for more details.
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.
Regards,
Steve
int qsize = 262140, arglen = sizeof(int);
setsockopt(socket, SOL_SOCKET, SO_SNDBUF, &qsize, arglen);
You'll want to check the return code is not -1 in case this fails for some reason. Man setsockopt for more details.
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.
Regards,
Steve
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP