Advertisement

06.28.2004 at 12:10PM PDT, ID: 21040872
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.4

Closing a multi-threaded UDP receive socket

Asked by robkl in Linux Programming

Tags: , ,

This questions pertains to closing a socket from a different thread while blocking on recvfrom(). It appears that the recvfrom() does not return when the socket is closed. I've looked around for an answer to this and I don't seem to find a satisfactory solution. This works identically on Linux as well as on Solaris 2.6 and 7. It appears that this may be a bad thing to do?

What I have is a class that encapsulates some of the socket API functions. This class is used for creating a socket to allow receiving UDP datagrams asynchronously.  Once the socket is created, a thread is created which waits for datagrams (in a blocking recvfrom() call) and places them in a shared buffer. Everything seems to work fine until I try to close the socket. When I close the socket from the main thread, the recvfrom() does not return, so the thread is blocking indefinitely (e.g. on shutdown).

I have implemented this under WIN32 and when calling closesocket() the recvfrom() returns immediately and things work as expected.

Any ideas of how I can get recvfrom() to return when the application is not receiving datagrams and the application needs to exit? (without making recvfrom a non-blocking call)
Start Free Trial
 
Loading Advertisement...
 
[+][-]06.29.2004 at 03:56AM PDT, ID: 11424593

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: Linux Programming
Tags: blocking, linux, non
Sign Up Now!
Solution Provided By: sunnycoder
Participating Experts: 2
Solution Grade: A
 
 
[+][-]06.29.2004 at 05:10AM PDT, ID: 11425070

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 7-day free trial to view this Assisted Solution or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32