Re: ssh processes lingering after scp

These are just zombies,  most likely someone is executing this script with a
nohup and bacgrounding it.  and then is logging out before the script finishes.
--- Susan McConnell <susanm@jbpc.co.uk> 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 is:
>
>         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 the
> 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 line
> 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 anyone
> shed some light on why this is happening and how we can fix it?
>
> Thanks for any help or ideas.
>
> Sue


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com