FallBackToRsh no -oBatchmode problem

[Shailesh Joshi]

Hello,

I am trying to use ssh as another user using
ssh -l Srvr. The keys have been exchanged. ssh works properly without any problems.
But whenever ssh command is fired, a new process is created as follows
e.g.
username 4793 1 0 00:29:26 ? 0:00 /usr/bin/ssh -x -oFallBackToRsh no -oBatchmode yes -loracle db01 scp -t /scratc

The process does not terminate and keep on running unless I kill it.

What this process is? Why is it created? Does it have any side effects? Why is the parent process '1'?

Thank You,
Shailesh

[Steven E. Protter]

Parent process id of 1 means it thinks the first process is its parent.

That makes it hard to kill and you are lucky you can kill it.

I do not believe any process should be created and left open with a solid ssh installation.

Would you please run the process with the -v switch and provide diagnostics. It might be very useful.

SEP

[Shailesh Joshi]

Hi Steven,

I am using ssh from cgi script. Only through cgi i face this problem. If I try to execute it from prompt, the problem does not replicate. Could CGI be the reason for this problem?

I tried using -v -v -v. On screen it shows the output. But when given through script it does not display debugging information.

Thanks,
Shailesh

[Shailesh Joshi]

Today we realized that the problem is caused by scp command and not by ssh command.

In /etc/ssh/ssh_config file, FallBackToRsh is set to 'no', but still whenever any scp command is fired, corresponding FallBackToRsh process is initiated. The process keeps on running indefiniately. We discovered that we had around 1500 such processes running on our server. We had to kill them all, but now whenever we run any scp command, the new FallBackToRsh process starts.

scp -v -v -v output shows

scp -v -v -v test.ksh oracle@db_server:/home/oracle
Executing: program /usr/bin/ssh host db_server, user oracle, command scp -v -t /home/oracle
Sending file modes: C0700 1878 id_test.ksh
id_test.ksh 100% |************************************************************| 1878 00:00

Do we need to change any other parameter in ssh_config?