On Monday 19 November 2018 07:34:20 Chris Nighswonger wrote: > On Sat, Nov 17, 2018 at 12:56 PM Nathan Stratton Treadway < > > [email protected]> wrote: > > On Sat, Nov 17, 2018 at 12:00:49 -0500, Gene Heskett wrote: > > > But without the logdir on the cli as --logdir=/path/to, it still > > > doesn't work because planner, although it does read amanda.conf, > > > does not pickup the logdir entry in amanda.conf. And I just found > > > that the configure disallows the setting of logdir as its a > > > deprecated method. > > > > > > That damns us to specifying the --logdir on the cli, and I believe > > > we should not use the same path as in amanda.conf, > > > > Yes, in v3.5 the planner --log-filename option tells the program > > where to write some output, and it required. For these manual runs > > you don't care about the info it writes there, so you just need to > > specify some out-of-the-way place for it to write to. > > > > Since it's creating the file in question, and normally is passed > > that argument by amdump which has already gone through the process > > of building a log file name to use, the planner executable itself > > does not look at the "logdir" config setting. > > > > (Note that the config option is "logdir", i.e. a directory, while > > the planner command-line argument is a full > > path-to-a-specific-file-name -- two different beasts.)
And I assume the file needs to be touched first? Got it. Thanks Chris. Copyright 2018 by Maurice E. Heskett -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
