Happen to catch this, this morning... Good dig on this..
Tcpserver *defaults* to a maximum of 40 simultaneous connections, so
this could very well be where your problem is.. Sorry, should have
thought of this earlier.
You can raise this limit with the -c n (n=number) option..
Please see
Hi Justin,
--On Sunday, March 14, 2004 11:37:13 AM -0500 "Justin Baugh, KSC"
<[EMAIL PROTECTED]> wrote:
So, after much testing & debugging:
* The problem only happens with tcpserver
* The problem is not replicable in any way under 5.2.1R
* The problem happens with any service/user with tcpserve