Re: 1.1.8-2 tcsh 6.10-1 inetutils-1.3.2-10 ( rshd + tcsh problem )

["Mad Dave" <dave at ook dot demon dot co dot uk>]

Thanks for the reply.  The problem is any comands I execute through the rshd
execute slowly due to the CPU going to 100% cpu usage, even when I run the
rshd as the user who is performing the rsh.  Since I only use the tcsh
though I have found a work around for the problem.  If I change the default
shell for the user who is doing the rsh to say /bin/tcsh.sh where tcsh.sh
contains the following:

if [ "$1" = "" ]
then
  tcsh
else
  tcsh $1 "$2" &
fi

Then everything works fine.  This script seesm to get executed by the bourne
shell which has no scripts which get executed at startup (on my system
atleast) so the script is executed quickly.  If $1 is empty then it must be
an interactive login via rlogin, which seems to work ok, else it must be a
request from the rshd so I lanuch a tcsh with the correct arguments into the
background and it seems run at the proper speed without going to 100% cpu
usage.

I think I have configured my cygwin environment exactly how I need it now
and it works fine.  Thanks to everyone who contributes to the project for
the work they put in..

----- Original Message -----
From: "Corinna Vinschen" <cygwin@cygwin.com>
To: <cygwin@cygwin.com>
Sent: Saturday, February 17, 2001 8:12 AM
Subject: Re: 1.1.8-2 tcsh 6.10-1 inetutils-1.3.2-10 ( rshd + tcsh problem )


> On Fri, Feb 16, 2001 at 11:50:21PM -0000, Mad Dave wrote:
> > If I connect via the rsh daemon as a user who has a default shell of the
> > tcsh, say by doing a command like 'rsh machine "echo hello"',  the
server
> > machines cpu usage jumps up to 100% and stays there for several minutes
(it
> > is tcsh that is eating up all the cpu time not the rshd).  I do have a
> > fairly large number of scripts that get sourced from the .tcshrc file,
but
> > if I was to rlogin to the machine it returns a prompt practicaly
instantly.
> > Anyideas as to why this is happening ?  Or any solutions ( other than
not
> > using the rshd ) ?
>
> No. The solution is in fact, don't use rshd but sshd. rshd is for
> reasons often mentioned in this mailing list not able to change
> the user context. That's a problem! Using ssh and sshd with RSA
> key _is_ definitely the better way - not only for security reasons
> (/usr/doc/Cygwin/openssh-2.3.0p1.README).
>
> There is another way, though. Start inetd from the user account
> which shall run rshd and the subshell. And don't forget to set
> the user permissions then (/usr/doc/Cygwin/inetutils-1.3.2.README).
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Developer                                mailto:cygwin@cygwin.com
> Red Hat, Inc.
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
>


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple