On Sat, Oct 26, 2002 at 10:58:53PM -0500, Fraser Campbell wrote:
> Hi,
>
> Someone responded to me off-list suggesting I look at etimeout. I increased
> it from 300 to 600 and the problem did disappear, on rereading the FAQ it
> seems so obvious now :-(
>
> Is there a way to determine exactly how long amanda is taking with the
> estimates?
Almost the first line of the amdump reports shows the total estimate time.
Not individual disklist entries, but total time.
I just grep'ed the last two weeks of reports for fun.
Estimate Time (hrs:min) 2:29
Estimate Time (hrs:min) 1:54
Estimate Time (hrs:min) 2:11
Estimate Time (hrs:min) 2:14
Estimate Time (hrs:min) 1:51
Estimate Time (hrs:min) 1:48
Estimate Time (hrs:min) 1:48
Estimate Time (hrs:min) 7:32
Estimate Time (hrs:min) 1:29
Estimate Time (hrs:min) 1:32
Estimate Time (hrs:min) 1:16
Estimate Time (hrs:min) 1:17
Estimate Time (hrs:min) 1:16
Estimate Time (hrs:min) 1:15
Couple of things intrigued me.
The 7+ hour one came from a night when one system was down and
apparently, long ago, I raised my etimeout value to a large value.
The second thing is why are my estimates getting shorter?
Consistantly about 2 hours then dropping to 1.25 hours recently.
Strange :)
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
