Solaris

Hi All

I have a separate thread ListenerThread having a socket listening to info broadcasted by some remote server. This is created in my main thread.

Because of requirements, once the separate thread is started I need to avoid any blocking function on the main thread. Once it comes to the point to exit the application I cannot perform a join on the listener thread so the only thing I can do is to KILL it.

My questions are:

what happens to the network resoruces allocated by the function passed to the thead? Is the socket closed properly or there might be something pending? ( most worried about this )

is this procedure fast enough i.e. is the thread killed so that interrupt immediately ?

I am working with Linux ...what command or what can I check to ensure that there is no networking resource left pending or that something went wrong for the Operating system? whatever might be pending...

I am a bit scared that the killing of the application is not fast enough to guarantee that the exit of the application is clear.

I thank you very much for your help

Regards MNSTN

NOTE: I am using boost::thread in C++

A socket is a file descriptor. All file descriptors have an implicit close() performed on them during image rundown. When you close a listener socket fd the port will likely go into TIMED_WAIT state.

If TIMED_WAIT is not a problem the socket part is pretty clear.

Am not clear on your resources question - do you call pthread_exit() from main - or the equivalent of that- on signal receipt? Or are we talking signals you cannot block? pthread_cancel()?

Unfortunately I don't have a lot of exposure yet to pthreads.

I was looking for a a way to kill a thead in the fastest and no blocking way since I cannot call any blocking function to exit my.... so I was finding some KILL function able to kill a thread without having too much impact on the OS i.e. I am scared about having some socket left open /pending or some other kind of possible leakage caused by a BRUTAL killing of a thread...