Thanks Greg,
I guess I should have been more clear, I felt the script explanation was
the most succinct way to illustrate what I'm trying to do. But, more
accurately, a 3rd party accounting package triggers the rsh session (via
CLI) on a RH mail server to administer accounts. So the situation is
such that multiple workstations may be submitting multiple rsh sessions
in rapid succession due to the way the accounting application is set up.
The data is passed via arguments to bash scripts that take over on the
server. My users are not proficient enough to verify successful
completion, nor is the application sophisticated enough to interpret
whether the rsh session completed successfully as each script spawns
it's own process and is thereafter abandoned by the app. I know, I
know, but frankly I'm pleased the thing will even launch the script at
this point so work with me - a script 'wait' will not bear fruit.
More importantly, are you insenuating this might be something I'll have
to 'work around'? After not experiencing this on my other server I felt
rsh sessions would execute in parallel, or at least be so fast it
wouldn't matter. Do I need to be looking at another remote protocol?
Is this typical?
Andy
*********** REPLY SEPARATOR ***********
Not knowing if there is another problem, what about using wait in
your
script ?
whoops, should have said there is a simple exp at
http://www.moongroup.com/~tjacobs
Regards
Greg W
IT Consultant Sydney Australia
*********** REPLY SEPARATOR ***********
On 4/12/99 at 22:33 Andy Brown wrote:
>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.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
