gnreeke
June 6th, 2007, 12:53 PM
I have a working amanda system to which I just added a new client.
The amcheck fails when the system has been unused for a while, but works
if I login to the client and execute almost any command at all before running
amcheck on the server. Diagnosis: the machine shuts down the hard drives
when not in use for a while, so the amandad cannot come up soon enough to
respond to the amcheck (or actual dump) request.
I cannot find anyplace to make this timeout longer. Can someone tell me?
(I am still running amanda 2.4.5 because it works OK on my network. If
a timeout configuration parameter has been added on more recent releases,
I suppose it may be time to upgrade.)
Thanks,
George Reeke
The amcheck fails when the system has been unused for a while, but works
if I login to the client and execute almost any command at all before running
amcheck on the server. Diagnosis: the machine shuts down the hard drives
when not in use for a while, so the amandad cannot come up soon enough to
respond to the amcheck (or actual dump) request.
I cannot find anyplace to make this timeout longer. Can someone tell me?
(I am still running amanda 2.4.5 because it works OK on my network. If
a timeout configuration parameter has been added on more recent releases,
I suppose it may be time to upgrade.)
Thanks,
George Reeke