Re: How limits are enforced (was: various maxproc limits)
Re: How limits are enforced (was: various maxproc limits)
- Subject: Re: How limits are enforced (was: various maxproc limits)
- From: Terry Lambert <email@hidden>
- Date: Thu, 6 Oct 2005 13:27:44 -0700
On Oct 6, 2005, at 10:01 AM, Yefim Somin wrote:
RE: driving the load on Mac remotely.
Leaving the limit of 128 pty's alone for now, I have found that
trying to
drive just one scripted load through a telnet connection may work
for a
short sequence but is very flaky. The tool I am using (RTE freeware
for
which I have source) opens a telnet connection and then sends a
sequence of
strings taken from a script file in response to patterns received
from the
target system, e.g.:
~Rin: ~Sadministrator~T0-0
~Rrd:~S<password>~T0-0
~Rtor$ ~Sls~T0-0
~Rtor$ ~Sexit~T0-0
~DONE
Here ~R is followed by the expected pattern, ~S is followed by the
string to
send in response, ~T is followed by the designated delay in
seconds. The
above script logs in, does "ls" command and exits. ~R parts
describe tails
of the appropriate prompts.
I have tried the above sequence repeatedly on several Mac machines
from
different sending platforms with varying delay values, and it works
about
half of the time with the other half just getting stuck somewhere
in the
middle. It always works when the target is some other platform (Unix
flavors, Windows, etc.). Is there something I could do to
investigate it
further or is it a case for submitting a bug?
Best regards,
Yefim
Note that input will be flushed after the password prompt prior to
the read to get the password (to prevent people from scripting logins
like this, to make automated brute-force attacks more difficult), so
you probably need to delay a bit before sending your input. I have
no idea if the ~T delay you are talking about is a pre or post-delay
on the ~S, so I can't tell if this would be your issue. If it's a
post-delay, then it's likely the problem.
Your best bet would be to enable logging in RTE (assuming it even
supports it).
If you still can't see the problem, you probably want to create a cut-
down test case and file a bug including the source code for your cut-
down test case that demonstrates the problem.
-- Terry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden