Gene Heskett on Tue 29/07 13:20 -0400:
> >>     planner:        CONFIGURE_COMMAND="'./configure'
> >> '--host=i686-pc-linux-gnu' '--build=i686-pc-linux-gnu'
> >> '--target=i386-redhat-linux-gnu' '--program-prefix='
> >> '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin'
> >> '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share'
> >> '--includedir=/usr/include' '--libdir=/usr/lib'
> >> '--libexecdir=/usr/lib/amanda' '--localstatedir=/var/lib'
> >> '--sharedstatedir=/usr/com' '--mandir=/usr/share/man'
> >> '--infodir=/usr/share/info' '--enable-shared'
> >> '--with-index-server=localhost'
> >> '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists'
> >> '--with-smbclient=/usr/bin/smbclient' '--with-amandahosts'
> >> '--with-user=amanda' '--with-group=disk' '--with-gnutar=/bin/tar'"
> >> planner: defs:  DEFAULT_SERVER="localhost"
> >> DEFAULT_CONFIG="DailySet1" planner:       
> >> DEFAULT_TAPE_SERVER="localhost"
> >
> >One of those configure-time localhost's might be screwing
> >things up...
> 
> Virtually guaranteed.  Amanda is network aware, and
> localhost could be any machine, the original poster should
> please use the FQDN and rebuild his install.

I don't see how it's guaranteed, or even likely.  If
anything, those only set defaults, is that not correct? On
client machines using amrestore interface, the hostnames are
provided.  I don't see how specifying `localhost' is any
problem at all.

Anyways, my problem appeared to be a kernel bug.  i moved
from Linux 2.4.22-pre2 to 2.4.22-pre10 and this problem has
since disappeared.  It even worked after rebooting -pre2,
but after a few days the same problem would reappear.  Very
strange, and I'm not sure what between -pre2 and -pre10
fixed it (changelog doesn't show anything that might be
related), but it seems to work now...