Hi!
Thanks. I've been experimenting a lot, and now seems to have *solved* it.
What I did was to include the .gvfs in the exclude dirs, but it did not
work with /home/magnus/.gvfs, but finally with ./magnus/.gvfs. Which
makes me curious about your exclude-list, that utilizes the full paths,
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
On 01/28 11:46 , Carl Cravens wrote:
I've written a little tool to help analyze BackupPC scheduling that I
thought others might find useful. It is meant to generate plots that can be
viewed from the web, but it's just as easily used from the command line.
So, my goal was going to be rsync on all machines, I seem to have that
working fine now on my windows machines, but my work laptop is part of a
domain so I figured I would try rsyncd and learn how it worked in the
process. It is trying to backup, but it is not following my rules
correctly. It is
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 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
