Re: dar_manager: dar process fails

Am Samstag, den 18.07.2020, 15:21 +0200 schrieb Denis Corbin:
> On 18/07/2020 07:57, Volker Wysk wrote:
> > Am Freitag, den 17.07.2020, 19:40 +0200 schrieb Denis Corbin:
> > > On 16/07/2020 18:03, Volker Wysk wrote:
> > > > There isn't any -a/--alter argument in the command line. Looks
> > > > like the dar_manager (parent) process introduces it an sends it
> > > > to the dar subprocess. >
> > > 
> > > Correct. So remains the point to know how such
> > > --alter=ignore-order (or -ai in short) got passed to dar from
> > > dar_manager (but there is not only command line that feed the
> > > arguments to dar):
> > > 
> > > Can you check the database does not include this argument to be
> > > passed to libdar:
> > > 
> > > dar_manager -B /mnt/sk1/Sicherung/Kataloge/D2020-07-16-03-04-34
> > > -l | grep "dar options"
> > 
> > % dar_manager -B /mnt/sk1/Sicherung/Kataloge/D2020-07-16-03-04-34
> > -l
> > 
> > dar path        : dar options     :  --no-warn=all --fsa-scope=none
> > --alter=ignore-order --restore home/v/abc database version: 4
> > 
> > 
> > archive #   |    path      |    basename
> > ------------+--------------+--------------- 1       Archive
> > A2019-07-29-14-31-04 2       Archive B2020-06-06-04-22-34 3
> > Archive C2020-07-12-07-09-10 4       Archive D2020-07-16-03-04-34
> > 
> > 
> > I guess that those "dar options" are used for all invocations of
> > dar_manager with the specific database. How did it get there? I
> > don't have it in my other databases (it's empty there). Looks like
> > I accidentially saved those options in the database.
> > 
> > I've been able to remove those options with "dar_manager -B
> > /mnt/sk1/Sicherung/Kataloge/D2020-07-16-03-04-34 -o".
> > 
> > So "-o" (and "--extra") saves the specified options in the
> > database file. That's not what I want. I want to specify the
> > options for only one call of dar_manager.
> > 
> > 
> 
> then you should rather use -e option than -o option. See dar_manager
> man page for details :)

The documentation of -o doesn't mention that the arguments will be
stored in the database. I also couldn't find it mentioned somewhere
else in the dar_manager man page. I also don't know for sure what those
stored arguments will do, and what they are for.

From the documentation of -e, I should have looked more closely, but I
thought that the (only) difference was that -e takes one argument
(containing several arguments for dar), whereas -o takes a list of
arguments. 

Could you please add information, what those stored dar options are
about?

Cheers,
Volker