> > So, you'd end up with:
> > - /usr/share/backuppc/config.pl # default config file
> > - /etc/backuppc/config.pl # local main config overrides
> > - /etc/backuppc/$host.pl # per-PC config overrides
> The last should of course be /etc/backuppc/pc/$host.pl. Thanks for
> clarifying that for me.
> I've suggested to the Debian maintainer that per-PC config files be kept in
> the pc subdir for Debian as well.
For the virgin release (by default) it's /etc/BackupPC/config.pl
and /etc/BackupPC/pc/$host.pl (note the capitalization).
Debian uses /etc/backuppc.
> Just wondering if this is inching any closer to the top of your ToDo
> list :-)
> No rush. Just a friendly reminder so it does not get completely forgotten.
> I personally still feel that it would be worth implementing. But if you
> don't like the idea, that would be fine by me too. I enjoyed working on the
Sorry about the long delay in replying. While I'm concerned about
the additional complexity, I agree it makes sense. One significant
benefit is that merging the main config file on upgrade will no longer
be necessary (I'm not sure all distros do that currently).
I'll plan on getting this in the next major release (which after
3.1 is likely going to be 4.0).
From: Frans Pop <elendil@pl...> - 2008-03-13 14:23:57
The thread yesterday on the -user list reminded me that I never replied to
this mail. So this time my apologies for the long delay.
One reason is that I've picked up my activities in Debian again, so I've had
less time for other projects.
On Thursday 15 November 2007, you wrote:
> Frans writes:
> > Just wondering if this is inching any closer to the top of your ToDo
> > list :-)
> > No rush. Just a friendly reminder so it does not get completely
> > forgotten.
> > I personally still feel that it would be worth implementing. But if you
> > don't like the idea, that would be fine by me too. I enjoyed working on
> > the patch.
> Sorry about the long delay in replying. While I'm concerned about
> the additional complexity, I agree it makes sense. One significant
> benefit is that merging the main config file on upgrade will no longer
> be necessary (I'm not sure all distros do that currently).
You probably know what Debian does: prompt the user that there are
differences and leave it to him to sort out how to merge them. This can be
tricky, especially if there have been many local changes in the config.
> I'll plan on getting this in the next major release (which after
> 3.1 is likely going to be 4.0).
That's great. The thread yesterday shows there is certainly demand for it.
Have you already started on that? Anything I can do to help?
As I've mentioned before my knowledge of perl is limited and I probably
won't be able to help with any trickier bits, but this patch still has my
I'm certainly willing to help work out remaining implementation details and
migration issues and to run tests.
If a file has been renamed or moved it looks like rsyncd/BackupPC jobs
will redownload the file even though the file is already in the pool
I'm currently perusing the sources to see if there is a way to work
around that. Has anyone already investigated this? Am I headed down a
Maybe some kind of a callback out of RsyncP to see if a checksum is in
the pool already?