I think you're having some confusion about what that clause in authorized_keys
does. According to [1], it basically executes the command for you. So when the
backuppc user creates the ssh connection, it runs:
'/usr/bin/rrsync /'
on the target. You don't need to "initiate" the rsync in this way be
This is the command in authorized_keys:
command="/usr/bin/rrsync /",restrict,from=
So it should allow rsync to access to the full server, as expected,
but BPC doesn't show any files in the backup
Il giorno gio 23 mag 2024 alle ore 10:24 Gandalf Corvotempesta
ha scritto:
>
>
Il giorno gio 23 mag 2024 alle ore 09:16 Christian Völker via
BackupPC-users ha scritto:
>
> Well, I guess you'll need to make sure ssh works fine.
> To do so, go to your backuppc server an switch into the user context of
> backuppc by "su - backuppc". From there issue "ssh user@hostname" and
> ac
Well, I guess you'll need to make sure ssh works fine.
To do so, go to your backuppc server an switch into the user context of
backuppc by "su - backuppc". From there issue "ssh user@hostname" and
accept the public key of the target client.
Once done, it should run without any problems. As long
