Re:Indy Rsh 9.0 More Problems
Quote
> I tryied the rsh componenet with rshd for LInux and it was OK.
It's not working for me on FreeBSD 3.3.
Quote
> the only
> problem wa that I can run just about 30 sessions and then the server is
> going now. You have to restart inetd in order to get it back on-line.
There doesn't seem to be any problems with the server as we have other
programs that continue to happily log in and do their business. As a matter
of fact, if you wait for the second command to time out, you can run another
(third) command successfully. Then the next command (fourth) times out again
as well. Perhaps it's not disconnecting properly?
Quote
> All this happens of you do your calls verry fast. If you hve enought time
> bnetwin them (30 calls / hour) you won't have this problem.
Like I said this happens on the second command, and regardless of how fast I
do it.
I didn't have any problem with subsequent commands when running 8.1 beta,
which leads me to believe the problem is with the Indy implementation.
Somewhere between that 8.1 build and the 9.0 build something was changed in
some way that broke it for me (although the UseStdError problem *was* fixed.
I'll see if I can find a copy of the 8.1 build and compare the code...
Greg
Quote
> All this is
> coused by the implementation of the winsock. the same is the situation
with
> windows rsh server component and winsock.
> --
> Doychin Bondzhev - Team Indy
> doyc...@dsoft-bg.com
> DdSoft-Bulgaria
> http://www.dsoft-bg.com
> "Gregory Wood" <gr...@com-stock.com> wrote in message
> news:3b60d9b0$2_1@dnews...
> > Having yet more problems with Rsh in Indy 9.0. Now that I've upgraded to
> the
> > latest beta build (just grabbed it before sending this message), I'm
happy
> > to report that UseStdError now works properly. Unfortunately, I'm not
able
> > to execute more than a single command without problems. The first
command
> > works brilliantly, but the second command times out with a 10060 socket
> > error. I confirmed this with the Remote Shell Demo in the hopes that I
was
> > just doing something wrong.
> > Any ideas?
> > Greg
