Le 14/09/2021 à 03:34, Adam Goryachev via BackupPC-users a écrit :
On 14/9/21 02:00, Juergen Harms wrote:
This is not the place to fight for being right, but to understand and
document help for users who hit this kind of problem.
Trying to understand: how do you define separate and different
profiles ("per-host override configs") for each of your 18 different
PCs in one single .pl file (i.e. your file at
/etc/backupp/hostname.pl) ? or do you mean by hostname.pl a list of
specific files where hostname.pl stands for an enumeration of 18 files
with PC-specific names?
I suspect he means 18 files with each file representing the specific
config for that specific host. This is the way BackupPC is designed,
global config in config.pl and specific config for a single host in
hostname.pl. There are extensions to this whereby you could have config
which is specific to a group of hosts in a group.pl and this is
"included" into each of the hosts within the group, but that is outside
the scope of this discussion.
If the latter is the case, our disagreement is very small: each of
these files in /etc/backuppc provides config info for one pc, and the
pc/ directory does not harm, but is not used (I tried both variants -
with and without specifyint pc/ - both work)
The "pc" symlink (it's not a directory within the Debian package) is a
compatibility layer to make the Debian package compatible with the
standard BackupPC documentation and user expectations outside of the
Debian community. So if you asked for help on the list, you might be
advised to create a host config file BPC as etc/pc/hostname.pl, assuming
you are unaware of any specific details, you might navigate to
/etc/backuppc/pc/ and create a hostname.pl file. This will work as
expected. If you were aware, you might navigate to /etc/backuppc and
create the hostname.pl file, which would have the exact same result
(working as expected).
IMHO, it would appear that you had some config issue, and because things
were not working you looked for something to blame, the pc symlink
looked strange, and so you blamed that (at least that is what I did in
the past). Once you understand that this is just a massive non-issue and
totally not relevant to any perceived issue, then you can ignore it and
move on.
Regards,
Adam
_______________________________________________
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/
Yes, like Adam wrote I mean one configuration file for each host which
needs override, so you get:
/etc/backuppc/config.pl << common options
/etc/backuppc/host1-overrides.pl
/etc/backuppc/host2-overrides.pl
/etc/backuppc/host3-overrides.pl
...
You don't need one configuration file for every host defined in
/etc/backuppc/hosts, only those with special needs that deviates from
the main configuration (different transport method, specific shares
exclusions...).
Lately I found that with a little work on the main config.pl I need very
little in the hosts override configuration files, and only for a few of
them. So the clutter in /etc/backuppc is minimal, just for my esthetic
satisfaction. ;-)
Regards.
_______________________________________________
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/
