Hi Glad to see the list back. My problem is more of a trouble shooting nature. I have a server application running on Linux that validates information from telecom type customers. A vendor of the systems that ask for this validation just migrated their system from NT to Solaris. The link (socket type) between our systems runs 24/365 or is supposed to anyway. Either the Solaris application or operating system drops the link. At first we thought it was during extended periods of no transmissions. There are no keep-alives going through the socket during these idle times. But during system testing they crash the system intentionally to make sure it will auto recover. Anyway, sometimes both ends think the link is down but we can't reconnect to restore it. My application should kill the socket and go back into listen mode. This is a one on one situation. If I allow two systems to come in, they go on two different ports. My question is two part. 1) Is there some setting on the Solaris that may be causing it to not close the socket even though an application may think it is down? 2) Is there a way to find out what is connected to the socket when this happens. The customer platform is half way across the country and tcpdump won't allow me to run it remotely. Oh, and I'm not sure if this matters but the other vendor wrote their system in Java so they could move platforms w/o rewriting the code. Larry Griffin
begin:vcard n:Griffin;Lawrence tel;cell:(210) 269-7708 tel;fax:(210) 829-4220 tel;work:(210) 576-1174 x-mozilla-html:FALSE org:Southwest DataCom Corp. adr:;;P.O. Box 460485;San Antonio;Texas;78246;USA version:2.1 email;internet:lgriffin@texas.net x-mozilla-cpt:;22400 fn:Lawrence Griffin end:vcard
