Hi there,
On Fri, 7 Jun 2019, David Wynn wrote:
I?ve just noticed that there are two directories ...
The fact that you have one of your IP addresses appearing some place
it probably shouldn't be makes me wonder if you've made a typo in a
configuration file, but I couldn't swear to it.
Looks like you might have installed BackupPC from more than one, er,
source. In the interests of their own sanity, package maintainers for
the likes of Debian, Ubuntu and derivative distributions do (shall we
say) interesting things with the files and directories used 'upstream'
by the authors of the packages. At the same time they will often make
choices which mean that the package as provided by the distribution's
compressball or whatever doesn't really suit what one is trying to do.
Add to that the facts that there are differing takes on what filesystem
'standard' (for want of a better word) should guide us, and that not
all the packages one might need are available in all distributions, and
the result is sometimes a right royal clusterfest. Drives me nuts.
The StudlyCaps version ('BackupPC') is from the package authors, the
lower case version ('backuppc') looks to me like a Debianated version.
Despite my loathing for StudlyCaps, even if I'm using a distro like
Debian I generally prefer that over the lower case variety because it's
what the authors orignally wrote and it makes it easier to make sense
of e.g. conversations on mailing lists.
If you really care about it I'd suggest renaming anything that you're
fairly sure you aren't using to something nonsensical, or moving it to
a directory where it can't possibly be used, reboot, and then, if (say
in a few years) nothing bad seems to have happened you might feel it's
safe enough to delete the renamed things. But I tend to just leave it
be, eventually I'll probably pension the system off and start afresh.
Of course I have the luxury of not having to explain it to anyone else
most of the time.
Alternatively you could try to wade through all the assorted files and
directories to see what gets used by what. You'd probably need to go
back to examine the original installation files and figure out if you
changed anything which might have a bearing. Best of luck with that.
When I'm doing that sort of thing I find writing everything I do in a
notebook can help. If you need to document it you will need it tidy.
Personally I like everything to do with configuration to be (a) under
/etc and (b) named as the package authors named it. Then I might have
a fighting chance of knowing where I am with it all. Much of the time
that means installing from source, rather than using packages, and a
more than cursory glance at whatever installation notes there are.
Your rsync problem _probably_ isn't related to this issue. I've seen
a few problems when newer rsyncs wouldn't talk to older ones because
of the lack of (default) shared encryption mechanisms. This happens
especially when you work with more than one system or distribution or
release of same, and some of them aren't as up to date as the others
for perhaps perfectly good reasons. Same thing happened with SSH too.
Best I can suggest is crank up the debugging levels and log everything
you can until you find something, maybe try using Wireshark too, and
don't be afraid to dig into the code and put some 'print' statements
in to add to what sometimes might be less than informative logging.
Just my 2 * $currency_units, HTH. I've glossed over a few things. :/
--
73,
Ged.
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
