Bruce Thayre wrote:
Hi Matthias,
Ah I see, I guess I shouldn't mix bash notation when asking about a
command I run in a shell. So what you recommend is exactly what I've
been doing. Assume my router is MyRouter.domain, and the client behind
the router is MyClient. In MyClient's
Hi Everyone,
Some more info on this problem which could hopefully bring some help
my way. I dinked around in the backuppc_dump script and had it dump out
the config values it was getting for the client I'm testing. Oddly
enough it appears as if it's not reading my config file at all...it
Sorry for the spam but I found a bit more info. The ClientNameAlias I
set via the cgi interface found it's way into my
/etc/Backuppc/config.pl. Looks like it set it for my server, and not my
actual host. Backuppc user/group owns the directory my top directory
partition is mounted on, so I'm
On 13/12/12 12:21, Bruce Thayre wrote:
Sorry for the spam but I found a bit more info. The ClientNameAlias I
set via the cgi interface found it's way into my
/etc/Backuppc/config.pl. Looks like it set it for my server, and not
my actual host. Backuppc user/group owns the directory my top
Hi Adam,
Thanks for the input! Setting the per-pc config info kicked backuppc
into generating a per-pc config file in /etc/backuppc like you
predicted. However, in changing the top directory I thought it would
look in /new_top_dir/pc/ for my host config files? Apologies for the
spam as
Hmm, more spam...ConfDir is only for the main config and hosts file,
not host's files. I may just scrap my current config and just have it
read all the per pc stuff from /etc/BackupPC/pc/. I'd prefer it
otherwise, but I'll probably waste more time any other way. Thanks for
your help Adam!
On Wed, Dec 12, 2012 at 7:49 PM, Bruce Thayre btha...@physics.ucsd.edu wrote:
Hmm, more spam...ConfDir is only for the main config and hosts file, not
host's files. I may just scrap my current config and just have it read all
the per pc stuff from /etc/BackupPC/pc/. I'd prefer it otherwise,
Hi Matthias,
Thanks for your prompt reply! I gave your recommendations a try and
had no luck. Setting CLIENT='name as in $Conf{ClientNameAlias}' doesn't
actually substitute the value for ClientNameAlias. Bash doesn't know
the config file, so just returns that as a string if I try to ping
Bruce Thayre wrote:
Hi Matthias,
Thanks for your prompt reply! I gave your recommendations a try and
had no luck. Setting CLIENT='name as in $Conf{ClientNameAlias}' doesn't
actually substitute the value for ClientNameAlias. Bash doesn't know
the config file, so just returns that as a
Hi Matthias,
Ah I see, I guess I shouldn't mix bash notation when asking about a
command I run in a shell. So what you recommend is exactly what I've
been doing. Assume my router is MyRouter.domain, and the client behind
the router is MyClient. In MyClient's respective config file I have:
Bruce Thayre wrote:
Hello Everyone,
I've been a maintainer of an old install of backuppc until our server
recently died. I've reinstalled and brought all other services back
except for backuppc. Many of our backup clients are behind routers and
I had been using the ClientNameAlias
Hello Everyone,
I've been a maintainer of an old install of backuppc until our server
recently died. I've reinstalled and brought all other services back
except for backuppc. Many of our backup clients are behind routers and
I had been using the ClientNameAlias option in their respective
12 matches
Mail list logo
