-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-05-10 at 01:48 +0200, Carlos E. R. wrote:
I expected the "real" time to be large, as I was doing other "heavy" things (a kdar backup that crashed), but the "user" time I expected to be
I found an interesting thing. I'm doing a test run of dar - after kdar
crashed I saw the command line it uses and it is not so difficult - and I
then told it to use "par". I thought it was going to use "par", but no,
to me surprise it uses par2:
...
Adding file to archive: /usr/share/susehelp/mecreating PAR file for file
/Grande/kdar/system_backup_10.2_20070509.2.dar ...
par2cmdline version 0.4, Copyright (C) 2003 Peter Brian Clements.
...
Block size: 585000
Source file count: 1
Source block count: 2000
Redundancy: 2%
Recovery block count: 40
Recovery file count: 1
and it is the version I compiled, too. Curious!
The dar command is told to use par via the option:
-B /usr/share/doc/packages/dar/dar_par.dcf
which runs that script at the end of each dar slice, I understand. It
contains:
# configuration file for dar to have Parchive integrated with DAR
# to be passed to dar as argument of -B option
# either directly on command line or throw $HOME/.darrc or /etc/darrc
# files
create:
-E "/usr/share/doc/packages/dar/dar_par_create.duc %p %b %n %e %c 2"
# 2 stands for 2% of redundancy
# adjust it to your needs
test:
-R "/usr/share/doc/packages/dar/dar_par_test.duc %p %b %n %e %c"
# note, that you may need to set the path to dar_par_test.duc
# and dar_par_create.duc
So, for creation it calls
"/usr/share/doc/packages/dar/dar_par_create.duc", which in turn contains
this:
# change according to you need
PAR=par2
I did not touch that, it is dated "2006-11-25". Funny that SuSE contains a
script calling a program they do not supply. Maybe I'll bug the bugzilla
chaps a bit ;-)
(The par calling code is:
exec $PAR c -r$6 -n1 "$1/$2.$3.$4"
with the positional parameters being:
<path> <basename> <slice number> <extension>