I finally, after much wrestling, got a single computer installation of the 3.2.0 beta1 release, amanda-3.2.0_beta1.tar.gz, compiled and running on Ubuntu 10.10 (a pre-release, as it is due out in about a week).
Initially I compiled with no arguments to ./configure. That produced a problem where amanadad refused to run except as user "amanda" and the server ran as "backup". I then recompiled with: ./configure CLIENT_LOGIN="amanda" --with-user=backup --with-group=backup I'm no expert on configure, so that could be wrong. BTW, are the options for configure documented anywhere? That done, I was able to get an amckeck, a backup and a recovery, verified by diffing the two trees. With 1 DLE, amcheck takes about 7 seconds to check the client. However, approximately every other use of the client results in no service at the amanda port: # netstat -a | grep amanda # syslog reports (may wrap on your MUA): -------------------------------------------------- Oct 4 20:22:16 meerkat xinetd[25867]: Started working: 1 available service Oct 4 20:22:25 meerkat xinetd[25867]: file descriptor of service amanda has been closed Oct 4 20:22:25 meerkat xinetd[25867]: select reported EBADF but no bad file descriptors were found -------------------------------------------------- I worked around this by restarting xinetd. Nothing in the log files jumps out at me. -- Charles Curley /"\ ASCII Ribbon Campaign Looking for fine software \ / Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com / \ No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
