How do I know how many dumpers are active? I just changed my config to
allow 2 while i figure out this problem with the disk. It said both
dumpers
were active, but there were no dumper processes on the one client box
in my disklist file.
Robert
--
:wq!
--
>How do I know how many dumpers are active? ...
Amanda will start the number you tell it to. The real question is,
how well are they being used. The easiest way to tell is with amstatus.
In particular, running it against a completed amdump. file.
For instance, I have this as part of my "run-a
>Date: Thu, 09 Nov 2000 18:42:16 -0500
>From: "John R. Jackson" <[EMAIL PROTECTED]>
>>How do I know how many dumpers are active? ...
>Amanda will start the number you tell it to.
Up to MAX_DUMPERS (which in my copy of server-src/driverio.c is 63).
>The real question is,
>how well are they bei
>Up to MAX_DUMPERS (which in my copy of server-src/driverio.c is 63).
True.
>amplot is handy for this, as well ...
Also true.
>(What's "broken" about it...?)
It doesn't generate any of that output I posted :-(. I'm guessing it
might be because the dump was finished, so it skipped over doing
At 05:42 PM 11/9/2000, John R. Jackson wrote:
>[...]
>For instance, I have this as part of my "run-amanda" script right
>after amdump (the syntax may be different at 2.4.1p1 -- I forget):
>
> amstatus ${config} --summary --file amdump.1
>
>Since the most recent amdump. file is always amdump.1, t
>Looking at the amstatus code in 2.4.2 indicates the output you indicated
>*is* displayed if you pass the --stats option.
Thanks. I used to have a mix of 2.4.1p1 and 2.4.2 and I don't think
this arg used to be needed.
>However, I don't see any way to get that output using 2.4.1p1.
I don't rem
"John R. Jackson" wrote:
>
> >(What's "broken" about it...?)
>
> It doesn't generate any of that output I posted :-(. I'm guessing it
> might be because the dump was finished, so it skipped over doing some
> things that might show up while it's still running.
On my SuSE amanda-2.4.1p1-7 here,
