Look in the XferLOG.XX for localhost and look at the "Running:" line and see what it says (and paste it back).   It may be because you're using $argList+ instead of $argList.  I think if you're running locally, you don't need to escape the commands.  Just a thought. 

On 3/20/06, Trasher <[EMAIL PROTECTED]> wrote:
Hello,

I have some problems using backuppc with rsync with sudo on my localhost.
Here is the config file using ssh :
$Conf{BackupFilesOnly} = ['/etc', '/boot'];
$Conf{XferMethod} = 'rsync';
$Conf{XferLogLevel} = 1;
$Conf{RsyncShareName} = '/';
$Conf{ArchiveComp} = 'bzip2';

This one works perfectly (using the main config.pl $Conf{RsyncClientCmd} = '$sshPath -q -x -l root $host $rsyncPath $argList+';)

When I try to use sudo for my localhost, the file becomes :

$Conf{BackupFilesOnly} = ['/etc', '/boot'];
$Conf{XferMethod} = 'rsync';
$Conf{XferLogLevel} = 1;
$Conf{RsyncShareName} = '/';
$Conf{RsyncClientCmd} = '/usr/bin/sudo $rsyncPath $argList+';
$Conf{RsyncClientRestoreCmd} = '/usr/bin/sudo $rsyncPath $argList+';
$Conf{ArchiveComp} = 'bzip2';

Using this one, $Conf{BackupFilesOnly} seems simply ignored, backuppc proceed on all / (including the disk where the backuppc data directory is [/media/secondary/]).

Did I make a mistake in the $Conf{RsyncClientCmd}?
The tar method always fails on this host, that's why I tried to use rsync.

I've checked mailing list archives without luck :-(
Great thanks for any help and for this wonderfull backup solution :)
Johan
--
Get Firefox!

Reply via email to