Am 2018-08-04 um 09:34 schrieb Sven Schlittermann: > "Stefan G. Weichinger" <[email protected]> writes: > >> I know about the 2 parameters >> >> flush-threshold-dumped >> flush-threshold-scheduled >> >> but how to make sure that *all* the planned dumps are done before >> writing to tape? > > I had to do this some yeary ago because my holding disks were too > slow. From brain-internal memory...: > > First I ran amdump without taping. Overriding the tape device with > /dev/null by calling "amdump -o tapedev=/dev/null" . > > And after amdump finished, automatically call amflush. > > Drawback is that you get two amreport mails.
In recent versions of amdump you also have the options: amdump <conf> [--no-taper] [--no-dump] [--no-flush] ... Yes, sure, that would be a solution ... but not the most elegant one. thanks, Stefan
