From: Steve W. <swa...@ls...> - 2003-07-15 11:46:35
|
On Tuesday, July 15, 2003, at 03:19 AM, Lammersdorf, Lorenz wrote: > hi all, > > just another question about inclucing per-pc conf-files. i have to > backup 3 > servers: > > host dhcp user moreUsers > 130.7.42.17 0 supervisor > 130.7.42.18 0 supervisor > 130.7.42.19 0 supervisor > > so i made 3 cnfig.pl's that are placed in a directory called > /raid/backuppc/conf/machinename/. > my /raid/backuppc/conf/config.pl contains the following do-statements: > > $Conf{SmbShareName} = ''; > do '/raid/backuppc2/conf/130.7.42.17/config.pl'; > do '/raid/backuppc2/conf/130.7.42.18/config.pl'; > do '/raid/backuppc2/conf/130.7.42.19/config.pl'; > > but unfortunatly, all machines try to mount the SmbShareName specified > in > the 3rd config.pl (from machine 130.7.42.19). what's my mistake? > > thnks > > lorenz Your path names look a little odd to me, but I just recently started using BackupPC, so there might have been a change in the migration to version 2.0.0. What has worked for me is to create a master config file /usr/local/backuppc-data/conf/config.pl that contains the default settings. Then for each system that needs a slightly different config, place only the changes into /usr/local/backuppc-data/pc/computername/config.pl. You shouldn't need and do statements or anything like that. The server automatically scans for these per-PC config files and reads the data when necessary. It appears as though you would just create a file called /raid/backuppc2/pc/130.7.42.17/config.pl to override any default settings. Don't put anything in the per-PC config file that is really a default or you'll potentially run into trouble. (Ask me how I know. :-) You would use an include file in the per-PC config file if you wanted to make a common set of modifications to numerous clients and didn't want to worry about keeping them in-sync with the various per-PC config files. In this case, you would put the include statements in the per-PC config files and not in the global config file. Steve |