>I tried putting "amandaidx 10082/tcp" in /etc/services on the
>client ...
That was the right thing to do.
>... as read from the server ...
Huh?
>... which seemed to fix
>things until I actually got to an 'extract' and then amrecover
>failed with a similar error.
So did adding "amidxtape 10083/tcp" fix this as well?
>From the error message, I'm not exactly sure which file or
>directory "No such file or directory" refers to ...
"No such file or directory" is the text conversion of the Unix error code
ENOENT, however that error code is returned by all sorts of functions to
indicate "no entry was found". When Amanda called the routine to look
up "amandaidx/tcp" it got back ENOENT because you didn't have it listed
in /etc/services, then it translated that to text (also via a standard
system provided function) to "No such file or directory".
>( and I've run the
>'patch-system' on the client which should suggest that the client
>has been provided with what it needs ).
I've never been convinced patch-system has any chance of working given
all the various OS's Amanda runs on. Much better to read the installation
instructions and do what they tell you (IMHO).
>Paul Yeatman
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
