I need to use RSH sessions in rapid succession (if not in parallel) from
a script.  My problem is that the first RSH session works perfectly, but
rapid subsequent sessions are timing out.  I considered it might be a
reverse DNS lag, and disabled the -a flag on the rshd line of inetd.conf
(but left -lL), and changed my hostname entries in hosts.equiv to IP
addresses, to no advantage.  If I wait several moments between rsh'ing
from a prompt, everything works OK, but the delays obviously throw
everything out of whack from within a script.

My server isn't taxed by any stretch, and we're on a switched LAN, so
it's not a performance issue.  I didn't experience this problem in my
test config on RH6.0, but it popped up when I moved it to a RH5.2 server
(in case it matters.)  None of my logs are indicating failed
connections, and client side (-d)iagnostics seem to concur that the
connection authentication never seems to start (times out)- as if the
daemon isn't responding at all to the subsequent requests.

I'm hoping there's a setting I'm missing that limits the frequency of
RSH logins, or?

TIA,
Andy


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to