ssh issue: /usr/bin/ssh -x -oFallBackToRsh no -l
 

I am using scripted scp to backup files for my network... on one or two of my machines have lingering processes long after the backup is complete...

a copy of my process table:

# ps -ax | grep backup
13899 ? S 0:00 /usr/bin/ssh -x -oFallBackToRsh no -lbackup penguin2
13915 ? S 0:00 /usr/bin/ssh -x -oFallBackToRsh no -lbackup penguin2
13919 ? S 0:00 /usr/bin/ssh -x -oFallBackToRsh no -lbackup penguin2
13921 ? S 0:00 /usr/bin/ssh -x -oFallBackToRsh no -lbackup penguin2
13925 ? S 0:00 /usr/bin/ssh -x -oFallBackToRsh no -lbackup penguin2
27003 ? S 0:00 /usr/bin/ssh -x -oFallBackToRsh no -lbackup penguin2
27018 ? S 0:00 /usr/bin/ssh -x -oFallBackToRsh no -lbackup penguin2
27022 ? S 0:00 /usr/bin/ssh -x -oFallBackToRsh no -lbackup penguin2
27024 ? S 0:00 /usr/bin/ssh -x -oFallBackToRsh no -lbackup penguin2
27028 ? S 0:00 /usr/bin/ssh -x -oFallBackToRsh no -lbackup penguin2
29088 pts/5 S 0:00 grep backup

Anybody know what is going on here? I am indeed using scp and not ssh. I am assuming that scp is reliant on ssh and that these processes are invoked to help with the transfer. Why are they lingering though?

Thanks in advance...

I can't really answer your question, but I would check to make sure that there is no one on the network (or off :eek: ) ssh'd into your system. Probably not, but it's the first thing that popped into my head. Good luck.