> I was setting up backuppc and I had a small pbs. I put the right
> directory setup in BackupPC_admin cgi and I forgot to put
> the nearly same information in xxx/lib/BackupPC/Lib.pm .
> If you look at these information you have in BackupPC_Admin
> use lib "/home/backuppc/lib";
> and in Lib.pm
> TopDir => $topDir || '/home/backuppc/data',
> BinDir => '/home/backuppc/bin',
> LibDir => '/home/backuppc/lib',
> It recalled me some problems we add when setting up an application,
> till we decided our application merits to have its own file in /etc .
> I think that it should be the case for BackupPC. Just put a
> backuppc.conf file in /etc with all required information
> $EtcBaseDir = /home/backuppc;
> $EtcTopDir = $BaseDir + '/data';
> $EtcBinDir = $BaseDir + '/bin';
> $EtcLibDir = $BaseDir + '/lib';
> And use it in all file. It would regroup all informations
> for starting backuppc in a single point and ease a little the
> setup. From my point of view, backuppc really deserves that.
I don't think this is necessary. configure.pl should do all
the work for you.
I assume you were installing the CVS version? If so, you should
proceed by making a distribution (makeDist) and then unpack it and
run configure.pl. There's a chance configure.pl in CVS is broken
(I don't think I completely finished adding the debian-backuppc
init.d script), so perhaps this is why you had to do it manually.
Get latest updates about Open Source Projects, Conferences and News.