Hello Jan,
http://www.rts.uni-hannover.de/rtnet/lxr/source/include/rtnet_socket.h#L109
No, not rt_socket_release (is for internal use only anyway), *rt_socket_dereference*!
I am sorry, I must have had tomatoes on my eyes to just see the #109. (rt_socket_release() is around this line in socket.c so I just scrolled to there)
The problem I was thinking about is, as I realized, more an application problem: if a still referenced socket is released.
Then rt_socket_close returns -EAGAIN, and the application has to resolve this problem (if it is responsible for it e.g. by blocking a task which is accessing the socket), or it has to poll for the socket to become free (see the various examples).
Jan
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ RTnet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-users
