Re: ssh processes lingering after scp
From: Patrick Lapre (patrick_lapre_at_palletways.com)
Date: Wed, 6 Oct 2004 07:59:56 +0100 (BST) To: Susan McConnell <firstname.lastname@example.org>
Have you tried this script on other systems (just to verify it only
happens on this machine)? When did this occur? What version of SSH and
Perl are you running?
Just some questions to shed some light on the problem.
You could try a workaround like to filter out these processes (using a
grep) and kill them instead trying of trying to exit a shell and hoping
the process shuts down.
Implementation & Support-manager
On Oct 05, 2004 11:55 AM, Susan McConnell <email@example.com> wrote:
> We're copying a number of files, sometimes up to 3-400, using
> scp called from a perl script. The command issued by the perl script
> my $cmd = "scp $basedir/data/$basename remote.example.com:/tmp";
> system ($cmd);
> We're finding that some ssh processes, with a PPID of 1, remain after
> script has completed. "ps -ef" shows:
> UID PID PPID C STIME TTY TIME CMD
> root 12904 1 0 09:35 pts/0 00:00:00 /usr/bin/ssh -x ...
> root 12990 1 0 09:36 pts/0 00:00:00 /usr/bin/ssh -x ...
> root 12995 1 0 09:36 pts/0 00:00:00 /usr/bin/ssh -x ...
> root 13000 1 0 09:36 pts/0 00:00:00 /usr/bin/ssh -x ...
> root 13251 1 1 09:37 pts/0 00:00:00 /usr/bin/ssh -x ...
> The full command shown in each case (removed from above to prevent
> wrapping) is:
> /usr/bin/ssh -x -oFallBackToRsh no remote.example.com scp -t /tmp
> I've tried "shopt -s huponexit" but that hasn't resolved this. Can
> shed some light on why this is happening and how we can fix it?
> Thanks for any help or ideas.