Le 11/09/2021 à 09:23, Juergen Harms a écrit :
On 10/09/2021 09:18, Dave Sherohman wrote:
I'm not sure why Debian decided to do the pc/ symlink thing, but it
works. Debian was doing that with the BPC 3.x packages in debian10
and it never caused any problems that I'm aware of.
I am coming back to the symlink question, I did not take it seriously
enough. According to backuppc documentation (
http://backuppc.sourceforge.net/BackupPC-4.0.0.html, Config and Log
Directories) it is meant to point to a directory that contains per-pc
definitions - they serve to override definitions originally made in
config.pl but which are to be different for specific hosts.
As it is in the present Debian package, this symlink does more or less
nothing and does not at all allow to define per-pc configurationd - a
very important drawback. You say "it works" - what makes it look as if
it works is that in absence of such per-pc definitions the definition in
config.pl is used.
Juergen
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
Hello, I am using Backuppc 4 on Debian 11, migrated from a long running
Backuppc 3 installation. The symlink is a loop-back to the same
directory, where I store my per-host configurations. For me it works
perfectly, my overrides are applied as they should.
How did you test and notice that the per-host configurations were not
applied?
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
