> -----Original Message-----
> From: Jon LaBadie [mailto:jon AT jgcomp DOT com] 
> Sent: Friday, May 16, 2003 10:18 AM
> To: Rebecca Pakish Crum
> Subject: Re: Connection timed out: STILL A PROBLEM:long entry
> 
> 
> On Fri, May 16, 2003 at 08:59:37AM -0500, Rebecca Pakish Crum wrote:
> > I am still getting a timeout on one of my solaris clients. I have 
> > increased the etimeout in amanda.conf to 900!! Once again, 
> buserver is 
> > a RH8.0 running 2.4.2p2, client is a 2.6 running 2.4.2p2. I 
> have been 
> > running amanda on this for over a year with no problems.
> 
> 
> I forget the original messages, but "e"timeout changes the 
> estimate timeout. If that was too short you would get 
> messages about no plan -- "I think".
> 
> It looks like your dump started and failed.  If timeout was 
> the problem there, etimout would have no efffect.  Maybe 
> ?d?timeout?  I forget what the other is.

That makes sense now that you say it. The only reason I tried this was
because of information I found on the FAQ-o-matic about timeouts in
amdump.

I just looked at my amanda.conf
etimeout is now set to 900
dtimeout is set to 1800
and ctimeout is set to 60...and amcheck as no problems at all. 
Doesn't that seem strange??

<<winmail.dat>>