[rdiff-backup-users] ssh doesn't die after rdiff-backup completes

[Glenn Stewart]

Hi All,

 

I am currently experiencing issues with one of our instances of rdiff-backup.

 

----------------------------------------------------

Symptom:

 

After successful completion of a backup, ssh processes remain.

----------------------------------------------------

Method of execution:

 

FROM SERVER-A

/usr/local/bin/rdiff-backup --force /data server-b.domain.com::/directory

 

Which in turn runs:

/usr/local/bin/python /usr/local/bin/rdiff-backup --force /directory server-b.domain.com

 

This results in the following processes:

1a) /bin/sh -c ssh -C server-b.domain.com rdiff-backup –server

1b) ssh -C server-b.domain.com rdiff-backup --server

2) /usr/local/bin/python /usr/local/bin/rdiff-backup --force /directory server-b.domain.com

 

After process 2 completes the following processes remain:

1a) /bin/sh -c ssh -C server-b.domain.com rdiff-backup –server

1b) ssh -C server-b.domain.com rdiff-backup –server

 

If executing ssh commands directly, the ssh commands terminate after completion as expected.

Only rdiff-backup produces this result.

 

----------------------------------------------------

Versions:

 

Python 2.3.3 (#1, Mar 10 2004, 06:25:19)

[GCC 3.3.2] on sunos5

 

SSH Version Sun_SSH_1.0.1, protocol versions 1.5/2.0

 

 

Thanks in advance,

 

Glenn Stewart