>I'm still trying to get my laptop to connect to the amanda server.  I
>looked in the /tmp/amanda directory on the server, and found nothing; no
>log file was created.  ...

That's because your service stuff is messed up and no connection is even
being attempted.

>amandaidx/tcp unknown protocol
>
>I want to stress again that I *do* have the "amandaidx 10082/tcp" line
>in my /etc/services.

You can stress it all you want :-), but it's still broken.

Amanda makes a system call, getservbyname, to do a lookup.  That call is
returning "I have no idea what you're talking about".  Here's a little
test program to prove it:

  ftp://gandalf.cc.purdue.edu/pub/amanda/getservbyname.c

So the problem is, how is getservbyname() on your system doing the lookup?
It's apparently not looking at /etc/services (although you might want
to do an "ls -lLu /etc/services" after an attempt to see if the access
time is being changed).  I suspect you'll have to do some digging around
in your OS documentation and/or ask on one of those newsgroups/mailing
lists for how to make it look at the file instead of whatever it is
trying to do.

If the lookup sequence (i.e. "files" followed by "NIS" followed by tarot
cards) is not run-time configurable (e.g. with /etc/nsswitch.conf),
you may have built amrecover with a hard coded setup (e.g. NIS only)
that is going to be a problem on an emergency recovery setup.  If it is
run-time configurable, maybe you don't have that set up in your minimal
re-install setup.

If you get the little test program above working, or even with amrecover
itself, you might try a system call trace on it.  That may give some
clues about where it is looking.

Another idea is to skip using amrecover altogether.  It's not that hard
to figure out what tapes you need (look in the archives for "amr-all" or
the Amanda chapter for other details) and just run amrestore across the
network yourself.  That's really all amrecover is doing for you anyway.

>One item to note is that I do *not* have inetd running ...

You do not need it running on the client (laptop) to use amrecover (or
amrestore, for that matter).

>John

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Reply via email to