I just had a weird instance.

I run amcheck late in the afternoon so that if there are any problems,
I can fix them before the amdump run.

I'd installed 2.4.5p1-20051103 and had run ldconfig, then amcheck last
night before the amdump run.  Amcheck was completely happy then.

Last nights amdump run was, as near as I can tell, totally normal.

Nothing's been changed as I was in the shop much of the day, carving
metal for an improvement to my micromill.  So imagine my surprise when
I get to the amanda list and find a message from amcheck that the
client 'coyote', this machine, could not be contacted.

The only thing I could think of to do was to re-install
2.4.5p1-20051103 and re-run ldconfig again.  At that point, amcheck is
once again happy.

But I'm certainly curious if its going to happen again tomorrow after
the amdump run is completed tonight.  Has anyone else had a similar
problem with this release?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.35% setiathome rank, not too shabby for a WV hillbilly
Free OpenDocument reader/writer/converter download:
http://www.openoffice.org
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.