Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am new to the forum, please correct me if I am posting in the wrong forum..
While using UNIX domain sockets for IPC between two processes, the "Resource temporarily unavailable" error is thrown constantly. What are the possible options to fix the issue?
I have increased the receive buffer size at /proc/sys/net/unix/max_dgram_qlen . What other socket buffer sizes, relevant to unix domain sockets can result in this error??
Any inputs on the common problems that result in this error will be very helpful.
"Resource temporarily unavailable" is EAGAIN, aka EWOULDBLOCK... You will get it only on file descriptors that you have explicitly set to non-blocking I/O mode... And, it indicates that your I/O operation would normally have blocked at that point, because it couldn't occur immediately... (Ie: for reading, there's currently no data to read; for writing, the buffer is full and needs to be emptied first...)
Thank you very much for the links. Yes, that is exactly what I am trying to do - non-blocking I/O. As my processes are interrupted by signals, frequently, I have to receive, send in non-blocking mode. (The other option is to use select but even select is interrupted by signals!) So, I get the error during send/write, because the buffer(send/receive) is full. Other than, reducing the frequency of my IPC messages, I wanted to know what are the socket buffer sizes I could increase, that can possibly resolve the issue?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.