Le 11/09/2021 à 12:08, Juergen Harms a écrit :
On 11/09/2021 11:14, thveillon wrote:
Hello, I am using Backuppc 4 on Debian 11, migrated from a long
running Backuppc 3 installation.
Same for me, but - so far on Mageia
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.
That is good news, and I start to understand: keeping the per-host
definition files in the top-level directory (/etc/backupc) and having a
loop-back implies that at the first iteration, launched when backuppc
wants to see them, makes them accessible - at that pass the remainder of
the top-level nodes - significant at the first pass - will be ignored).
How did you test and notice that the per-host configurations were not
applied?
1. replaced the loop-back link by a link into a directory that contains
only the per-host (that worked on Mageia) ,
2. restarted backuppc (systemctl restart),
3. used the web interface (cgi) to launch a full backup for one of the
hosts subject to per-host definitions,
3. used the web interface to see what had been effectively saved
After reading your mail, I simply moved my per-host files (I have only
afew) to the top-level directory and replaced the link to the directory
with these defininitions by the initial loop-back. And that produces the
desired results. Many thanks!
But this is not how backuppc has been designed - the per-host
definitions should be in a separate directory. That is (but far from
copiously) documented in backuppc. What happens if someone has many such
hosts? the top-level directory will become a monster. And, an (infinite)
loop-back is not the cleanest imaginable approach for getting at these
definition files.
Juergen
By searching the changelog I found mention of a bug report #434793,
which led me to the message n°22:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436793#22
Quote:
"> Why was it decided to do this differently for Debian? Backwards
> compatibility with previous Debian versions maybe?
Yes, 2 reasons:
1- the debian package 1st introduced the config files in /etc (before they
were found in /var/lib/backuppc)
2- directories in /etc should have the same name as the package
so /etc/backuppc is used and not /etc/BackupPC."
/Quote
Debian is known for its idiosyncrasy, which often is part of the
distribution added value, sometime is just added fun for the
administrator...
_______________________________________________
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/
