On Thu, Jan 31, 2013 at 2:21 PM, Ctdi Unix wrote:
> I'm kind of a commandline junkie. So using a GUI anything is not really
> where I go. In my world a GUI is not a better/safer/more accurate way to
> edit anything. Why bother setting up special permissions for CGI access if
> you have root and
I'm kind of a commandline junkie. So using a GUI anything is not really
where I go. In my world a GUI is not a better/safer/more accurate way to
edit anything. Why bother setting up special permissions for CGI access if
you have root and can drive vi like a mad pengiun.
So no
:)
On Thu, Jan 31
On Thu, Jan 31, 2013 at 1:53 PM, Ctdi Unix wrote:
> Found it. And it has NOTHING to do with my config - and EVERYTHING to do
> with where the config is.
>
> OLD VERSION:: in the per-PC configuration file,
> //var/lib/BackupPC//pc/$host/config.pl.
> NEW VERSION:: __CONFDIR__/pc/HOST.pl per-pc con
Found it. And it has NOTHING to do with my config - and EVERYTHING to do
with where the config is.
OLD VERSION:: in the per-PC configuration file,
//var/lib/BackupPC//pc/$host/config.pl.
NEW VERSION:: __CONFDIR__/pc/HOST.pl per-pc config file
I was putting the client config in pc/lamp.config.p
On 31/01/13 14:45, Ctdi Unix wrote:
> Thank you for helping me.
>
> You are correct I killed it very quickly. Because in the previous
> version, the dump command would show the actual shares I wanted on the
> command line { and not / } and I would not get any messages like
> *Remote[2]: file has va
Thank you for helping me.
You are correct I killed it very quickly. Because in the previous version,
the dump command would show the actual shares I wanted on the command line
{ and not / } and I would not get any messages like
*Remote[2]: file has vanished: "/proc/2/exe"
*
which indicates it is *
On 31/01/13 04:26, Ctdi Unix wrote:
[SNIP]
>
> dump as a debug shows:
>
> *full backup started for directory /*
> *started full dump, share=/*
> *Running: /usr/bin/ssh -q -x -l root lamp /usr/bin/rsync --server
> --sender --numeric-ids --perms --owner --group -D --links --hard-links
> --times --blo
I have an old version running successfully. -> BackupPC-2.1.2-7.fc6
Now I am trying to get BackupPC-3.2.1-10.fc17.i686 working.
I passed the no error you can see "no service start" thing. It was some of
some weird FC17 thing. Now I can't get the most basic backup to run.
On the old version my
