Tony Gravagno wrote: > > This is one of the unfortunate issues of using sockets from MV. Part of > the problem is that the MV DBMS is an application over the OS, and the > handle to the socket is only released if the MV monitor explicitly releases > it. If you whack an MV process without allowing it to go through a proper > wrapup, then the host OS doesn't know that the socket should be available, > so SO$REUSEADDR is useless anyway. In the case of D3, the only way to > release a socket that's been whacked like this is to reboot D3 itself - a > major pain to get all users off the system to release a single socket - and > for this reason I discourage use of D3 as a socket server. I'd be > interested to know if U2 is any more adept at handling this scenario. I > guess it comes down to the definition of the word "whacked" and how well U2 > handles such conditions.
Well on D3 Unix/Linux no need to reboot D3 to release sockets, only on d3 windows, I think. I'm currently porting jd3 from d3 to universe in fact. Socket are okay for us with a program like jd3 Cedric ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
