I just wanted to submit a progress report that may help others along the path to AMANDA on the RISC as the information is really scattered all around.
I'm running Amanda-2.4.2p2 CC=gcc Running AIX 4.3.3 MR9 on H50 Compiled using directions here: http://www.backupcentral.com/amanda.html At the current I want to run backups on local machine only. An earlier post in this group ( 31015 ) had mentioned that there was trouble with a file during compile time called mntent.h in /usr/include so you should rename it and retry the compile. Compiled fine at that point. After much configuring and testing I ran amcheck and I got a host error and after looking into it a little further I stumbled across an error in the amindexd program. When executed manually I am getting the following error: amindexd: getpeername: Socket operation on non-socket. This error is refered to in several posts and on other sources. For instance in message ( 9315 ) someone had trouble running a recover because of this error. I managed to solve my host error issue and my check completes fine. That seemed to be mostly of my doing... I didn't have my .amandahosts configured properly and my disklist file didn't like the /dev/hdiskX format - so I changed it to /file/system/names. So at this point pretty much everything checks out but I'm wondering if I'll be able to do anything at all because the amindexd isn't running. I'm not a C programmer but if somebody had source I think I'd be able to compile it...to refer back to a previous message ( 3425 ) regarding the getpeername error Alexandre Oliva said: "It means that the process' stdin (the current tty) is not a socket, as amandad expects." ...continuing on to ( 3495 ) Mr. Oliva mentions that amcheck might run should you remove the raw device name and add the mount point (which in my case worked). But outside of my check working I don't understand enough about the program to resolve this getpeername error, nor could I find any relevant information on it outside of the fact that it was supposed to be fixed with the next version. Is it going to be an issue? If so how would I go about fixing it? Regards, Tony _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
