Date: Wed, 7 May 2003 09:35:33 -0500 (CDT) From: mark tinguely <tinguely@web.cs.ndsu.nodak.edu> To: freebsd-questions@freebsd.org Subject: Re: HELP: TCP stack problem in 4.8-R with rsh connects (second channel) Message-ID: <200305071435.h47EZXNK007323@web.cs.ndsu.nodak.edu>
next in thread | raw e-mail | index | archive | help
If I remember from your original posting that you are doing sequential rsh and eventually it starts giving time outs. I saw something like this starting in FreeBSD 3.0 when we use rsh to do sequential remote dumps (especially noticable on larger partitions). It acted like FreeBSD stayed in CLOSING state too long. A sleep (I chose 60 seconds because it worked) would let the previous rsh command to close before starting the next one. Obviously, you do not want to do that. I am just throwing this idea out to see if we can define the conditions that cause your problem. I don't have your original post, but I thought it was the one where netstat on each side had one side of the connection in a closing state but the other side had already remove the connection. It would be interesting to get the netstat of both sides when you are using the FreeBSD <-> Solaris and FreeBSD <-> FreeBSD. Does this problem existing in the FreeBSD <-> Solaris case when the role of FreeBSD and Solaris are reversed? --Mark Tinguely.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305071435.h47EZXNK007323>