I just wanted to follow up on this issue now that I have figured out the
cause.
I figured out why my per-host files weren't being used. It's always the
subtle things. :) I have been using backuppc since about 2004 or 2005. So
back then, I'm not sure whether it was in backuppc itself or in the Debi
Per-host config files are working fine for me. Maybe your
RsyncClientCmd has the rsync path hardcoded in it instead of referencing
$rsyncPath?
My environment is mostly-linux with a few BSD-based hosts and, to just
pick a .pl that contains "local" at random-ish, I have:
$Conf{RsyncClientPath
No Sir, No restrictions.
On Sat, Jul 24, 2021 at 12:59 AM Adam Goryachev via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:
> Sounds to me that you might have restricted your source IP in the *bsd
> .ssh/authorized_keys file. Maybe double check on those restrictions.
>
> Regards,
>
Sounds to me that you might have restricted your source IP in the *bsd
.ssh/authorized_keys file. Maybe double check on those restrictions.
Regards,
Adam
On 24/7/21 14:27, Brad Alexander wrote:
I ran across what appears to be the reason for the issue that I am
having. I found the following i
I ran across what appears to be the reason for the issue that I am having.
I found the following issue in my console:
/var/log/console.log:Jul 23 23:52:11 danube kernel: Jul 23 23:52:11 danube
sudo[2
866]: backuppc : command not allowed ; PWD=/usr/home/backuppc ; USER=root ;
COMMA
ND=/usr/bin/rsyn
I have been running BackupPC 3.x for many years on a Debian Linux box. I
just expanded my TrueNAS box with larger drives, grew my pool, and am in
the process of converting from BackupPC 3.3.1 on the dedicated server (that
has gotten a bit snug on the drive space) to a 4.4.0 install in a FreeBSD
jai